Re: /etc/resolv.conf changes every booting time
On Sat, Aug 05, 2023 at 10:52:35PM -0500, Nicholas Geovanis wrote:
> On Sat, Aug 5, 2023, 10:27 PM Greg Wooledge <greg@wooledge.org> wrote:
>
> > On Sat, Aug 05, 2023 at 10:05:31PM -0500, Nicholas Geovanis wrote:
> > > On Sat, Aug 5, 2023, 9:13 PM Greg Wooledge <greg@wooledge.org> wrote:
> > >
> > > > On Sun, Aug 06, 2023 at 09:28:55AM +0800, Jon Smart wrote:
> > > > > How to stop the auto-changes to /etc/resolv.conf after rebooting?
> > > >
> > > > https://wiki.debian.org/resolv.conf
> > > >
> > >
> > > Contrary to what that page states, auto changes to resolv.conf are never
> > > appropriate in the server environment. The statement there that it works
> > > fine in a "properly configured server" is the boilerplate escape hatch
> > for
> > > that inconvenient fact :-)
> >
> > Those words do not appear on that page. I don't know which sentence(s)
> > you're actually referring to.
>
>
> I'm referring to these exact words:
> "It also works well for many desktop and server systems, so long as the
> network infrastructure is perfect."
>
> Its a red herring because the DNS infrastructure in a data center is static
> at the IP address and host name level. And I feel certain that any network
> infrastructure constructed by humans is imperfect to some degree.
> There's their escape hatch.
Not all Debian systems are in a "data center". Sometimes they're on a
home network, or a workplace network. In both of those environments,
the DHCP server may be questionable -- either because it's being provided
by a cheap router (home), or because it's being managed by a different
department (workplace).
Some workplaces require the use of DHCP to configure network interfaces,
even when the DHCP server behaves in a way you do not wish. For example,
it may offer DNS nameservers that are not the ones you want to use. So,
many of us are running Debian systems where the IP address has to come
from DHCP, for political reasons, but the DNS servers that would come
from DHCP are *undesired*.
Therefore, we want to edit /etc/resolv.conf ourselves, and not let the
DHCP client daemon, or any other program, change it.
Therefore, this wiki page.
Do you have a specific wording change you'd like to see?
Is there any part of the page that is actually *incorrect*?
Are there any alternative solutions that are *missing*?
Reply to: