Public NTP (Network Time Protocol) Service


You are welcome to contact our NTP server to update your computer clock. To use the public NTP service, send me a message on the form below to let us know you're using our NTP server. Be sure to include your IP address or address range. Please see the first question below for conditions.

Ideally, please reference our NTP time server by name, If you must use an IP address (not recommended), the IPv4 and IPv6 addresses (which point to the same host) are currently:

You can also contact us by using on the form below.

Drydog NTP Timekeeper
Drydog Press Network Operations

NTP Access Request Form

IP Address, IP Address block, or IP Address range (free format):
Number of NTP servers you wish to connect directly with us
Comment (optional):

Please confirm:


Important Notice: In compliance with the Children's Online Privacy Protection Act of 1998, we do not accept requests from children under 13 years of age.

Frequently-asked Questions with Answers (FAQ)

And without further ado, here are the most frequently-asked questions (FAQ).

Q: Can I use your NTP server?
A: Yes. This server is for use by the public. Feel free to use it, subject to these conditions:

If these conditions bother you, please discontinue using the service now.

Q: How do I set up my NTP client software?
That depends on what software you are using. Please consult the documentation that came with your software. See above for the hostname of our NTP service.

Q: Where is software and documentation available?
A: NTP software, including pointers to commercial and non-commercial NTP software, is at

Q: I get a "connection refused" message when trying to connect to your server. What's wrong?
A: You're probably trying to connect to the wrong TCP/IP port. The NTP server uses UDP port 123 ("ntp"). Other time clients use other time protocols. That is, port 13 ("daytime"), 37 ("time"), or 525 ("timed"). None of these other protocols are supported by this server. Please make sure your client software supports "NTP" and not some other time protocol.

Q: I get a "no route to host" message when trying to connect to your server. What's wrong?
A: The most likely possiblity is your ISP's or your personal's "firewall" is blocking access to NTP's port, 123. Another possiblity is this server is down due to some hardware problem.

Q: How many users do you have?
A: Most days, I see traffic from approximately 500 distinct hosts.

Q: How available is this server?
A: The intention is to provide uninterrupted 7/24 service. However, as a practical manner, this server is available externally about 99% of the time. Most interruptions are due to network connectivity, followed by software issues, power failures, and hardware (usually disk) failures. I will try to keep you informed about network and service status. However, I reserve the right to discontinue this service at anytime without notice.

Q: What is the source of the time at
A: The machine syncs to three stratum 1 clocks, geographically distributed, operated by NIST.

Q: What timezone does your NTP server use?
A: None. NTP servers use "UTC" time (formerly "GMT" time), which is the same throughout the world. The timezone you are in doesn't matter to this NTP server. The translation to a time zone is handled completely by your NTP client software.

Q: What other network services do you provide?
A: Currently, the machine also serves web (http) and ftp. These are publically-accessible services, but I do not provide public hosting services.

Q: Why do you run this service?
A: Because I can. It takes very little time or computing resources and it is useful to many. This spirit of cooperative anarchy is one of the things that built the Internet that we know today, yet sadly, very few are still practicing it.

Q: Who are you?
A: I'm Dan Anderson. On the Internet, I'm most likely best known for writing the Solaris x86 FAQ and the Simple Whois Daemon. I've been running Internet servers continually since 1994 and I've been actively using the Internet since 1982.

I hope that you find this service useful. If you have any further questions or concerns, or you've just got something to say, feel free to contact me.

Timekeeper, domain

[Back to Top]

Experts Only: Infrequently-asked Questions with Answers

NTP (Network Time Protocol) was invented to synchronize computer clocks in an internet network environment. Unlike other time protocols (e.g., timed), NTP seeks to synch to the most accurate clock rather than "average in" errors from multiple time sources. Clock sources are categorized by stratums (levels) away from master clock sources (that have short-wave radio or GPS connections to the U. S. Naval Observatory).

If a master clock source isn't available, you can arbitrarily choose a system's local clock source (quartz crystal) and use it as your master time server. A crystal in a computer usually isn't an accurate or uniform time source, because of variations in temperature and because the crystals used are usually lower quality as those found your watch. This applies equally to cheap PCs or expensive Sun servers. Only DEC (now Compaq, later HP :-) Alpha servers actually try to use accurate crystals and even those still benefit from NTP. However, at least you can make it a uniform time reference across multiple systems.

NTP is useful for synchronizing the time for software distributed on multiple hosts (for example, RPC, Remote Procedure Calls). Most access control mechanisms use time stamps, and therefore require systems to have their time synchronized. Finally, another benefit of NTP is ensuring accurate timestamps in log files, which greatly aids diagnosting network and network software problems.

[Back to Top]


[Back to Top]


Last updated 3 March 2018.

If you have questions or comments, please send a message to Dan Anderson.