classic version 3 bug? - NTP

This is a discussion on classic version 3 bug? - NTP ; Hi All, I seem to remember that ntp version 3 had a bug where if one of its servers was offline during initialization, ntpd would skip it and no longer poll the server even though the server comes back up ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: classic version 3 bug?

  1. classic version 3 bug?

    Hi All,

    I seem to remember that ntp version 3 had a bug where if one of its
    servers was offline during initialization, ntpd would skip it and no
    longer poll the server even though the server comes back up later. Was
    this an actual bug? Can someone point me to the docs (or bug report).
    Or was I dreaming this up?

    Thanks

  2. Re: classic version 3 bug?

    Edmund Lau wrote:
    > Hi All,
    >
    > I seem to remember that ntp version 3 had a bug where if one of its
    > servers was offline during initialization, ntpd would skip it and no
    > longer poll the server even though the server comes back up later. Was
    > this an actual bug? Can someone point me to the docs (or bug report).
    > Or was I dreaming this up?
    >
    > Thanks


    I don't recall that to be the case. However, in version 3 OR 4,
    if you use a name for the server and the name can't be resolved to an address
    during initialization, the behavior is as you describe. This can happen
    if the DNS server is inaccessible and the NTP server's name is not
    resolvable through the hosts file or some other means.

    -Tom

  3. Re: classic version 3 bug?

    Tom Smith wrote:
    > Edmund Lau wrote:
    >> Hi All,
    >>
    >> I seem to remember that ntp version 3 had a bug where if one of its
    >> servers was offline during initialization, ntpd would skip it and no
    >> longer poll the server even though the server comes back up later.
    >> Was this an actual bug? Can someone point me to the docs (or bug
    >> report). Or was I dreaming this up?
    >>
    >> Thanks

    >
    > I don't recall that to be the case. However, in version 3 OR 4,
    > if you use a name for the server and the name can't be resolved to an
    > address
    > during initialization, the behavior is as you describe. This can happen
    > if the DNS server is inaccessible and the NTP server's name is not
    > resolvable through the hosts file or some other means.
    >
    > -Tom


    One clarification....

    Version 4 is, I believe, different with regard to temporary DNS failures
    in that it will retry those later. In the specific example above
    (inacessible DNS server) version 4 might tolerate that whereas
    version 3 would not. Both will knock the NTP serer off the list
    if they get a permananent failure (NXDOMAIN) DNS response.

    -Tom

+ Reply to Thread