Re: Why does resolv.conf keep changing?
- Date: Wed, 25 Oct 2017 14:16:38 +0200
- From: <tomas@xxxxxxxxxx>
- Subject: Re: Why does resolv.conf keep changing?
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, Oct 25, 2017 at 01:06:37PM +0100, Joe wrote:
> On Wed, 25 Oct 2017 07:35:35 -0400
> Gene Heskett <gheskett@xxxxxxxxxxx> wrote:
> > Whereas my theory has always been WRT the search line, that it should
> > first search the /etc/hosts file for a name match, and failing that,
> > query my router, which is running dd-wrt which means its running
> > dnsmasq.
> Yes, but that information (among other stuff) lives in
> /etc/nsswitch.conf, not /etc/resolv.conf.
> Keep up at the back: why use one configuration file when a couple of
> dozen will easily do the job?
To be fair, those two do quite different things. The one is the
configuration for the (host name) resolver, whereas the other is
a configuration for generic name services (which encompasses many
other things, like user names, protocol names... you name it).
So nsswitch is "outside" as seen by the resolver.
Of course, one might envision one highly-integrated naming service
doing "all of that", and that was probably Sun's original vision.
But things like the DNS are complex (and important) enough that
they develop a life of their own.
The usual balance between integration and granularity which makes
the engineer's bread and butter, I guess.
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----