Robie is right. In the failure case the resolver is contacting
127.0.1.1, where the NetworkManager-controlled dnsmasq process listens,
rather than 127.0.0.1, where BIND named is listening.
Robie is right, too, in saying that the instructions you followed have
to be reinterpreted for Ubuntu. In Ubuntu /etc/resolv.conf is a symbolic
link to the file /run/resolvconf/resolv.conf which is dynamically
generated by the resolvconf utility. You can't edit /etc/resolv.conf
directly; instead you have to configure the software that sends
nameserver information to resolvconf.
If you are running BIND named locally to provide general name service
then you should almost certainly disable the NetworkManager-controlled
dnsmasq process and use the local BIND instead. To disable the
NetworkManager-controlled dnsmasq process, comment out the line
"dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf, then
sudo stop network-manager
sudo killall dnsmasq
sudo start network-manager
Next, configure BIND named to register its listen address with
resolvconf. Edit /etc/default/bind9 and change "RESOLVCONF=no" to
"RESOLVCONF=yes", then do
sudo service bind9 restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1101002
Title:
Frequently stops working for 15-30 seconds at a time on Ubuntu 12.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1101002/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
