On Mon, 15 Aug 2016 03:25:01 -0700 Rick Moen <[email protected]> wrote:
> Quoting richard lucassen ([email protected]): > > > 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. On my workstations I have no caching DNS. There is one in the network that's the one that is in dhcpd.conf. And even though you have an caching resolver, if your network settings are wrong during boot, there is nothing to be gained with a local resolver ;-) R. -- richard lucassen http://contact.xaq.nl/ _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
