-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 07:35:35AM -0400, Gene Heskett wrote: > On Tuesday 24 October 2017 23:46:47 Felix Miata wrote: > > > Gene Heskett composed on 2017-10-24 22:52 (UTC-0400): > > >> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote: > > >>>and made immutable. Particularly is the fact that /etc/resolv.conf > > >>> isn't a link to something else but contains: > > >>> > > >>>nameserver 192.168.XX.1 > > >>>search host dns > > >>>domain coyote.den
This seems wrong (I know, I'm late to the party). The way I read resolv.conf's man page (and my hazy memory), "search" lists *domains* to be appended to the host name to be resolved if that is incomplete. For example: my resolv.conf has a line search lan (whoever put that in there, but it's irrelevant on my laptop anyway). If I try to resolve just "foo", the resolver will first try "foo.lan" (duh, that's most probably wrong), then just "foo". If I give an FQDN (e.g. duckduckgo.com), the dots in the host name tell the resolver to bypass the search list. "host" and "dns" seem like wrong things to put in "search". The search entry above looks to me like something which should be in /etc/nsswitch.conf, like hosts: files dns meaning: "when looking for a host name, look first in /etc/hosts (files), if that fails turn to the DNS (dns). As always, I might be wrong. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnwelkACgkQBcgs9XrR2kZAugCeP6rDs/BbSlluH5TXiI4O51qR f+0AmwZs5iEZlRs0yzj8DB/YcAjm3kSA =Wg4b -----END PGP SIGNATURE-----
