F21 System Wide Change: Default Local DNS Resolver

Simo Sorce simo at redhat.com
Wed Apr 30 19:03:48 UTC 2014

On Wed, 2014-04-30 at 12:16 -0430, Robert Marcano wrote:
> On 04/30/2014 01:17 AM, P J P wrote:
> >> On Wednesday, 30 April 2014 3:18 AM, Al Dunsmuir wrote:
> >> On my home LAN, I run my own DNSSEC-enabled server using F20 & bind 9.
> >> This  local server also is my DHCP and Samba server. As usual, dynamic
> >> clients  receive  the  LAN  local  domain  ID  and  DNS  server  ID
> >> automatically.
> >>
> >> How  does  this  proposed  change  affect my clients, or especially my
> >> server  (which  uses  NetworkManager  (not  Network),  and a static IP
> >> address?
> >
> >    This should work just fine. If you upgrade your F20 machine to say F22, it would have the default resolver running on with its entry in '/etc/resolv.conf'. One change you would need to do is to make it listen on or the on static IP address of your server. Your clients won't know that they are talking to a different DNS resolver.
> >
> > If your clients are upgraded to F22, NetworkManager there would make the local resolver talk to the one on your server, because it'll receive that name server configuration via DHCP.
> I think the parent post is refering to the local domain name, I have 
> read this thread and people talk about not touching ever the resolv.conf 
> file. What about domain and search lines? If NetworkManager will always 
> use, it should still modify resolv.conf with the domain name 
> received from DHCP

Why would you care for the domain name as provided by dhcp ?

By default you wouldn't want that as you roam with a fedora laptop on
completely untrusted dhcp networks that can push whatever crap as a
search path.


Simo Sorce * Red Hat, Inc * New York

More information about the devel mailing list