Path: utzoo!mnetor!uunet!husc6!mailrus!ames!pasteur!ucbvax!UDEL.EDU!Mills
From: Mills@UDEL.EDU
Newsgroups: comp.protocols.tcp-ip
Subject: Time server status
Message-ID: <8803301701.aa12486@Huey.UDEL.EDU>
Date: 30 Mar 88 22:01:52 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 17

Folks,

At this time all five fuzzball primary time servers (WWVB and GOES)
are back in service. However, it turns out that the present NTP time
daemon ntpd does not recognize when a server explicitly indicates that
its time is invalid, as when first coming up and before resynchronization
is complete. This condition is indicated when the two high-order bits of
the status octet in the NTP header are set, as described in the latest
documentation issued a month or so ago. I have reports that some VAXen
running domain-name servers get mighty sore when this happens, since
their caches... Well, you can figure that out for yourself.

Mike Petry is now working on a new ntpd daemon to conform to the latest
specs; however, it might be useful to update the present version to ignore
packets received with the bits set.

Dave