On Wed, Oct 25, 2017 at 01:59:42PM +0200, Alberto Luaces wrote:
Michael Stone writes:On Wed, Oct 25, 2017 at 12:16:49AM -0400, Gene Heskett wrote:On Tuesday 24 October 2017 23:02:39 Michael Stone wrote:On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote: >But since its worked flawlessly for years, please explain what IS > wrong with it. We've been over this before. Your "search host dns" line doesn't do anything at all as written, but will screw things up if copied in a different order by someone who doesn't know that it's simply broken.That still doesn't specify what IS wrong. Reading the now 5+ year old man page, the only change I might make is to change the dns string to nameserver. IP changed host to hosts too.What man page? Honestly, it seems like you're making things up at this point.Might be "man resolv.conf".
Can't be, that man page clearly says:
search Search list for host-name lookup.
The search list is normally determined from the local domain name; by default,
it contains only the local domain name. This may be changed by listing the
desired domain search path following the search keyword with spaces or tabs
separating the names. Resolver queries having fewer than ndots dots (default
is 1) in them will be attempted using each component of the search path in
turn until a match is found. For environments with multiple subdomains please
read options ndots:n below to avoid man-in-the-middle attacks and unnecessary
traffic for the root-dns-servers. Note that this process may be slow and will
generate a lot of network traffic if the servers for the listed domains are
not local, and that queries will time out if no server is available for one of
the domains.
It certainly doesn't say anything about putting "host" or "dns" or
"nameserver" in that line.
Mike Stone