-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, Nov 04, 2017 at 08:53:56PM +0000, Brian wrote: > On Sat 04 Nov 2017 at 08:03:02 -0400, Roberto C. Sánchez wrote: > > > On Sat, Nov 04, 2017 at 08:45:59AM +0100, to...@tuxteam.de wrote: > > > > > > Most of us fall into two classes: > > > > > > A. All static. Nobody changes resolv.conf. All is well. Admin writes > > > resolv.conf (and /etc/hosts and all). (the "classic") > > > B. Get IP address via DHCP (dhclient, NetworkManager, whatever else). > > > Whatever else writes to resolv.conf. User == admin mostly doesn't > > > even know what resolv.conf means, most of the time.
[...] > I'm not going to ask what an "intersection situation" is. It sounds very > technical. Touché :-) basically that means that you care about the content of your resolv.conf, but let some agent (e.g. resolvconf or dhclient) update it. You then bear the burden to understand what said agent is doing. But you learn something (my learning started with chattr +i and log watching, some moons ago). > But I thought anyone who used DHCP. and cared about it, would > realise they had ended up on the network they were connecting to. That > would include using that network's nameservers (unless they arranged it > otherwise). Precisely. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAln+K5wACgkQBcgs9XrR2kabmwCcCOgWMdfWM87Osa5H0qzWI1K6 zZYAn0l0IkHFS/HVegn+ZcsAXBycVpxh =/Pk6 -----END PGP SIGNATURE-----
