On 11/08/11 19:06, Clint Byrum wrote:
> Marking importance in bind as medium. I can see a definite need for the
> "FQDN" of the machine to always be addressable for services, and bind
> would need to work the same as other services that listen on "0.0.0.0".
> There are workarounds, and this is only some use cases, so Medium seems
> appropriate.
>
> ** Changed in: bind9 (Ubuntu)
>     Importance: Undecided =>  Medium

The Bind Manual from the latest ubuntu bind9-doc package says:

   If no listen-on is specified, the server will listen on
   port 53 on all IPv4 interfaces.

This statement is ambiguous. However, my /etc/bind/named.conf.options 
DID NOT contain a listen-on clause and yet it does not listen on 
0.0.0.0:53 (or :::53). It listens only on the explicit addresses of 
localhost (127.0.0.1) and my ethernet interface.


The Bind Manual goes on to say:

   When { any; } is specified as the address_match_list for the
   listen-on-v6 option, the server does not bind a separate socket
   to each IPv6 interface address as it does for IPv4....

This implies that the IPv4 listen addresses will be selected after 
enumerating the available interfaces. If true, then bind9 will not 
discover the 127.0.1.1 address assigned in the default hosts file 
because it isn't defined as an interface.


I tried a bypass of explicitly coding within the options section:

   listen-on { 127.0.0.1; 127.0.1.1; 10.1.252.11; };

After I restarted bind9, I was disappointed to see only:

tcp   0   0 10.1.252.11:53   0.0.0.0:*    LISTEN      15451/named
tcp   0   0 127.0.0.1:53     0.0.0.0:*    LISTEN      15451/named
udp   0   0 10.1.252.11:53   0.0.0.0:*                15451/named
udp   0   0 127.0.0.1:53     0.0.0.0:*                15451/named

... it still isn't listening on 127.0.1.1!

p.s. cvsd doesn't listen on 0.0.0.0:2401, but it probably doesn't
matter.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/604283

Title:
  network servers do not listen on 127.0.1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/604283/+subscriptions

-- 
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

Reply via email to