Your premise that: > he shouldn't need his local named to resolve the name of the time > server.
is right; one does not need a local named in order to resolve the name of a remote time server. But ... ... running a local name server with resolv.conf containing 127.0.0.1 is quite a common and accepted practice; it's called a "caching-only name server." A quick google will show the commonness of this approach on Debian: http://www.google.com/search?q=caching-only+nameserver+site:.debian.org&num=100&hl=en&lr=&sa fe=off&start=100&sa=N I suspect that the original poster has this configuration; certainly I do. And then we're back to the original problem: > ntpdate: starts too early on machines w DNS server This is definitely a bug in the ordering and should be reclassified out of "won't fix". If you need more information then please don't hesitate to contact me. Regards .. Alexis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
