Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Jul 2008 11:57:41 -0500
From:      Brooks Davis <brooks@freebsd.org>
To:        "Patrick M. Hausen" <hausen@punkt.de>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: dhclient and resolv.conf.sav
Message-ID:  <20080710165741.GA12966@lor.one-eyed-alien.net>
In-Reply-To: <20080710085234.GD38495@hugo10.ka.punkt.de>
References:  <20080710085234.GD38495@hugo10.ka.punkt.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--ibTvN161/egqYuK8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jul 10, 2008 at 10:52:35AM +0200, Patrick M. Hausen wrote:
> Hello,
>=20
> we have been bitten by something that obvoiusly
> is a feature, not a bug, but I do not quite understand
> the intentions and reasoning behind it.
>=20
> I have a host with manual interface and resolver configuration
> and an additional interface that should get it's IP address
> via DHCP. But only it's IP address and netmask, nothing else.
>=20
> The DHCP server used hands out only IP addresses/netmasks,
> no domain-name-servers, domain-name, etc. configured.
>=20
> Yet, if there happens to exist a /etc/resolv.conf.sav file,
> every renewal of the lease by dhclient overwrites the contents
> of /etc/resolv.conf with those of resolv.conf.sav.
>=20
> In my particular case the .sav file contained an internal
> nameserver that was used when I initially set up the host
> in the lab. This entry was of no use to the server after
> it had been deployed in our datacenter.
>=20
> Can anyone shed some light on the intended mechanism?
> Studying the dhclient-script was not too helpful, either.

I suspect the theory is that you can have a static resolv.conf around
that gets installed when there isn't anything else to use.  In practice,
I think it mostly causes problems.  I'm somewhat tempted to remove the
creation of the file and add something like a resolv.conf.default in
it's place.

-- Brooks

--ibTvN161/egqYuK8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (FreeBSD)

iD8DBQFIdj+EXY6L6fI4GtQRAodsAKCrXvq03hCPzTF1rejKcsaRYjZe2wCeJHn7
Nu9Eunid9vs0kOfqn36CBCQ=
=eJrT
-----END PGP SIGNATURE-----

--ibTvN161/egqYuK8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080710165741.GA12966>