Yes, I'd say that "wontfix" is appropriate unless someone comes forward
with a reason why ntpd *should* listen at 127.0.1.1.

P.S.  I earlier wrote the following.

> It appears that bind9 operates in the same way.
> I added a virtual interface eth0:0 with a bogus address 
> and named started listening on that without being 
> restarted.

I later discovered that this occurs because bind9 has a hook script in
/etc/network/if-up.d/ which does "rndc reconfig".

-- 
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:
  ntpd does not listen on 127.0.1.1, the IP address associated with the
  system hostname

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