Public bug reported:
Binary package hint: bind9
Bind appears to be listening on specific addresses rather than on all
interfaces. This wouldn't be a problem except that on modern Ubuntu
systems the local host name is configured in /etc/hosts to by on
127.0.1.1 rather than the same IP as localhost (127.0.1.1).
r...@hostname:~# netstat -nlp | grep named
tcp 0 0 192.168.1.71:53 0.0.0.0:* LISTEN
30752/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
30752/named
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
30752/named
udp 0 0 192.168.1.71:53 0.0.0.0:*
30752/named
udp 0 0 127.0.0.1:53 0.0.0.0:*
30752/named
r...@hostname:~#
The net result of this is that this command will fail ("Connection
timeout; no servers could be reached") on a normal install of ubuntu
with a bind9 install:
$ dig @`hostname` <any host name>
Whereas it should behave the same as:
$ dig @localhost <any host name>
I don't understand the motivation that Ubuntu had for setting '127.0.1.1
hostname hostname.domain' in /etc/hosts but given that it does, all
daemons need to support it.
** Affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
--
bind listens on 127.0.0.1:53 rather than *:53
https://bugs.launchpad.net/bugs/669751
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
