The O'Reilly book _DNS and BIND_ says:
[QUOTE]
10.4.3.2 Interface interval
We've said already that BIND, by default, listens on all of a host's
network interfaces. BIND 8 is actually smart enough to notice when a
network interface on the host it's running on comes up or goes down. To
do this, it periodically scans the host's network interfaces. This
happens once each interface interval, which is 60 minutes by default. If
you know the host your name server runs on has no dynamic network
interfaces, you can disable scanning for new interfaces by setting the
interface interval to zero to avoid unnecessary hourly overhead:
options {
interface-interval 0;
};
On the other hand, if your host brings up or tears down network interfaces more
often than every hour, you may want to reduce the interval.
[/QUOTE]
But when I tried it, named noticed right away that I had brought up an
interface. Will investigate further.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other DNS servers from starting
Status in “djbdns” package in Ubuntu:
Confirmed
Status in “dnsmasq” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “pdns-recursor” package in Ubuntu:
Invalid
Status in “pdnsd” package in Ubuntu:
Invalid
Status in “djbdns” source package in Precise:
Confirmed
Status in “dnsmasq” source package in Precise:
Triaged
Status in “network-manager” source package in Precise:
Triaged
Status in “pdns-recursor” source package in Precise:
Invalid
Status in “pdnsd” source package in Precise:
Invalid
Bug description:
As described in
https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
resolving, network manager now starts a dnsmasq instance for local DNS
resolving.
That breaks the default bind9 and dnsmasq installations, for people that
actually want to install a DNS server.
Having to manually comment out "#dns=dnsmasq" in
/etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays
that way, it should be moved to the bind9 and dnsmasq postinst scripts.
Please make network-manager smarter so that it checks if bind9 or
dnsmasq are installed, so that it doesn't start the local resolver in
that case.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
