Subject: misc/23283: ntp.conf: workaround for bad nameservers / finding more volounteers
To: None <gnats-bugs@gnats.NetBSD.org>
From: None <netbsd@fortytwo.ch>
List: netbsd-bugs
Date: 10/27/2003 09:42:23
>Number:         23283
>Category:       misc
>Synopsis:       ntp.conf: workaround for bad nameservers / finding more volounteers
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    misc-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Oct 27 09:43:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Adrian von Bidder
>Release:        
>Organization:
pool.ntp.org
>Environment:
Does not apply
>Description:
Hi,

I saw that NetBSD ships ntp to use the timeservers pool at pool.ntp.org as per <http://cvsweb.netbsd.org/bsdweb.cgi/src/etc/ntp.conf?annotate=1.4>

As the founder of the pool.ntp.org project, I think this is great! Two little things:
 - as some nameservers don't do a proper round robin (Sun nscd and apparently some M$ resolvers), you might end up getting the same timeserver address repeatedly. I have introduced {0,1,2}.pool.ntp.org to work around this. (Currently, this is done with CNAMES as a temporary hack. I will do this properly, and also document it when I get time).
 - would it be possible to add something like 'if your computer has a static IP address, please consider joining the timeserver pool' to the ntp.conf file? I see you already provide the URL to the project, and mention that it is a volounteer project, so perhaps this is sufficient, but I feel an explicit invitation would be clearer.

Greetings
-- vbi
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: