Quoting richard lucassen (mailingli...@lucassen.org): > When you have no network on the machine ntp notes that there is no > network, then it stops AFAIK. But if you have a wrong resolv.conf or > something like that you get the above mentioned timeouts.
Really? 'Wrong resolv.conf or something like that'? There shouldn't IMO be broken DNS any more on modern networked *ix hosts. Run a local recursive resolver and list 127.0.0.1 as the first resolv.conf entry. It's 2016, guys. Unbound: http://linuxmafia.com/faq/Network_Other/dns-servers.html#unbound Deadwood: http://linuxmafia.com/faq/Network_Other/dns-servers.html#deadwood dnscache: http://linuxmafia.com/faq/Network_Other/dns-servers.html#debian-djbdns PowerDNS Recursor: http://linuxmafia.com/faq/Network_Other/dns-servers.html#pdns-recursor -- Cheers, Arrq uryc qrpelcgvat EBG13? Nfx zr ubj! Rick Moen r...@linuxmafia.com McQ! (4x80) _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
