On Sun, 19 Aug 2007, Sam Mason wrote: > Date: Sun, 19 Aug 2007 21:23:01 +0100 > From: Sam Mason <[EMAIL PROTECTED]> > To: [email protected] > Subject: Re: [time] www.pool.ntp.org down? > Sender: [EMAIL PROTECTED] > > On Sat, Aug 18, 2007 at 07:22:32AM -0700, Nelson Minar wrote: >> Rob Janssen wrote: >>> It is clear that ntpd was designed on the assumption that an NTP >>> server is a solidly available resource that does not go away for no >>> reason. >> >> It's equally likely whoever wrote the code just thought to cache DNS >> lookup once for efficiency and never thought about the case where the >> DNS record would change. :-) > > I'm not entirely certain, but as far as I know it was a definite design > decision.
Yes ; it has been discussed for years now. The problem is that you don't want ntpd to wait until DNS comes up with an answer ; 'non-blocking' or 'asynchronous dns' is hard to do in a way that works on all platforms. Google for 'ntp asynchronous dns'. > Sam HPP ---------------------------------------------------------------- _ Henk P. Penning, Computer Systems Group R Uithof CGN-A232 _/ \_ Dept of Computer Science, Utrecht University T +31 30 253 4106 / \_/ \ Padualaan 14, 3584CH Utrecht, the Netherlands F +31 30 251 3791 \_/ \_/ http://people.cs.uu.nl/henkp/ M [EMAIL PROTECTED] \_/ _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
