Date: Mon, 5 Jun 2006 15:51:48 -0400 From: Damian Gerow <dgerow@afflictions.org> To: Lyndon Nerenberg <lyndon@orthanc.ca> Cc: freebsd-stable@freebsd.org Subject: Re: [OT] resolv.conf and dhclient Message-ID: <20060605195148.GJ99893@afflictions.org> In-Reply-To: <20060605131957.P74433@orthanc.ca> References: <44842282.6050409@veldy.net> <448428D8.5030501@orchid.homeunix.org> <20060605134049.GB99893@afflictions.org> <20060605131957.P74433@orthanc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Lyndon Nerenberg (lyndon@orthanc.ca) [05/06/06 15:49]:
: >I have two interfaces, one wired and one wireless. Both addresses are
: >negotiated via DHCP. However, I do /not/ want to use the DNS servers
: >provided via the wireless connection.
:
:
: interface "ath0" {
: supersede domain-name "orthanc.ca";
: supersede domain-name-servers 127.0.0.1;
: }
:
: interface "bge0" {
: supersede domain-name "orthanc.ca";
: supersede domain-name-servers 127.0.0.1;
: }
:
: And then just run a local instance of named.
And what happens when I'm connected at home, and need to view portions of
DNS that are only accessible to the wired network?
And what happens when I'm connected at work, and need to view portions of
DNS that are only accessible to the wired network?
How will my local named instance know where to look? What happens when it
can't query externally at work?
There are very legitimate needs for being able to swap DNS servers on the
wired connection, while ignoring those provided via the wireless.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060605195148.GJ99893>