default local DNS caching name server

P J P pj.pandit at
Fri Apr 11 19:40:39 UTC 2014


> On Saturday, 12 April 2014 12:56 AM, Dan Williams wrote:
> We want to make sure that any local caching nameserver that we do use
> doesn't rely exclusively on file-based configuration, or if it does,
> it's able to re-read that configuration file using SIGHUP or some
> seamless reload functionality.  It *must* also be able to load new
> configuration without dropping in-process DNS queries on the floor,
> otherwise users will experience hung DNS a non-trivial amount of the
> time.
> The better way is to add/remove zones + servers from dnsmasq over D-Bus,
> which NM does not yet do since the patches are not yet upstream, or to
> use some other socket-based protocol like unbound does with dnssec-trigger. 

  Sure, makes sense. This workflow bits need to be worked out still. File based configuration is just an example. Important is that dynamic name servers augment the local name server rather than replace it.


More information about the devel mailing list