Comment 23 for bug 90267

The ntp devs refuse to do a normal wild card bind and stick with what they have done. This has come up in comp.protocols.time.ntp quite a few times. Which I think led to the new interface scanning code in ntp 4.2.4 which has it's own problems when ntp is started before the network is up. I mentioned this in my 2007-03-10 post.

Starting ntp before the network is up also breaks name resolution for any servers that are specified by name. How can a server name be resolved to ip if the network is not up yet? The following is valid

server ntp.ubuntu.com
server 0.au.pool.ntp.org
server 1.au.pool.ntp.org
server 2.au.pool.ntp.org

but wil fail because the dns can not be reached because the network is not up.

These problems disappear if ntp is not started until after the network is up.