default local DNS caching name server

Simo Sorce simo at
Sat Apr 12 02:08:21 UTC 2014

On Fri, 2014-04-11 at 15:22 -0500, Bruno Wolff III wrote:
> On Fri, Apr 11, 2014 at 14:21:30 -0500,
>    Dan Williams <dcbw at> wrote:
> >
> >NM in F20+ already has a "dns=none" option that prevents NM from
> >touching resolv.conf, but obviously if NM isn't touching it, the DNS
> >information that NM gets from upstream or your local configuration needs
> >to get to the local caching nameserver somehow.  Which is what the
> >existing NM DNS plugins are for, like the dnsmasq one.
> If you are running a caching resolver you don't need the DNS information 
> from DCHP (except except for the hotspot issue) at all. For example, 
> dnscache can be used for this. (It doesn't do dnssec though, so wouldn't 
> provide what is wanted for the proposal.)

Not true, in many networks you want it, for example in corporate
networks. You really want to be able to resolve the local resources and
they are only resolvable if you consult the local DNS as provided to you
by DHCP.

For hotspots in public places that doesn't matter as much of course.


Simo Sorce * Red Hat, Inc * New York

More information about the devel mailing list