| 2010-03-08 04:49:02 |
André Pirard |
description |
Binary package hint: bind9
Using Ubuntu 8.10 (Intrepid).
I installed bind9 as a caching nameserver.
(BTW, kudos for the simplest BIND installation ever seen !!!)
But BIND could overload my router's NAT table with UDP DNS requests.
So, ... I uninstalled bind9.
BIND did not stop. I had to restart Ubuntu. But /etc/resolv.conf remained like this :
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search lan
==> DNS no longer worked.
Uninstall cleanup did not restore a working DNS state.
resolvconf's README is suggesting this :
$ sudo echo "nameserver 192.168.0.1" | resolvconf -a dummy
/sbin/resolvconf: line 79: dummy_new.4139: Permission denied
Turned on manual mode : workaround :
/etc/resolvconf/run/interface/ contained lo.named and NetworkManager
I removed lo.named leaving NetworkManager
/etc/resolv.conf became :
# Generated by NetworkManager
domain lan
search lan
nameserver 192.168.0.1
nameserver 192.168.0.1
Strange contents, but working again. |
Binary package hint: bind9
Using Ubuntu 8.10 (Intrepid).
I installed bind9 as a caching nameserver.
(BTW, kudos for the simplest BIND installation ever seen !!!)
But BIND could overload my router's NAT table with UDP DNS requests.
So, ... I uninstalled bind9.
BIND did not stop. I had to restart Ubuntu. But /etc/resolv.conf remained like this :
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search lan
==> DNS no longer worked.
Uninstall cleanup did not restore a working DNS state.
resolvconf's README is suggesting this :
$ sudo echo "nameserver 192.168.0.1" | resolvconf -a dummy
/sbin/resolvconf: line 79: dummy_new.4139: Permission denied
Turned on manual mode : workaround :
/etc/resolvconf/run/interface/ contained lo.named and NetworkManager
I removed lo.named leaving NetworkManager
After the next DHCP renewal, /etc/resolv.conf became :
# Generated by NetworkManager
domain lan
search lan
nameserver 192.168.0.1
nameserver 192.168.0.1
Strange contents, but DNS was working again.
|
|
