Jump to content

NTP pool

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Artoria2e5 (talk | contribs) at 00:16, 8 March 2025 (expand, update). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
NTP pool
URLwww.ntppool.org/en/
IPv6 supportYes
Launched2003; 22 years ago (2003)[1]

The NTP pool is a dynamic collection of networked computers that volunteer to provide highly accurate time via the Network Time Protocol to clients worldwide. The machines that are "in the pool" are part of the pool.ntp.org domain as well as of several subdomains divided by geographical zone and are distributed to NTP clients via round-robin DNS. The geographic zone selection is no longer unnecessary, as customized authoritative DNS servers that utilize geolocation software (geoip) is now used.[2]

As of May 2022, the pool consists of 3,126 active servers on IPv4 and 1,534 active servers on IPv6.[3][a] Because of the decentralization of this project, accurate statistics on the number of clients cannot be obtained, but according to the project's website, the pool provides time to 5–15 million systems.[5] Because of client growth, the project is in perpetual need of more servers.[6][7][8]

The more time servers there are in the pool, the lower the resource demand on each member. Joining the pool requires at least a broadband connection to the Internet, a static IP address, and accurate time from another source (for example, another NTP server, a DCF77 receiver, a WWVB receiver, or a GPS disciplined oscillator).

This project was started by Adrian von Bidder in January 2003 after a discussion on comp.protocols.time.ntp about abuse of the public stratum 1 servers.[9][10] The system has been maintained and developed by Ask Bjørn Hansen since July 2005.[11]

The NTP pool occasionally see NTP server misuse and abuse, mostly from corporate vendors with many users shipping buggy software.[12][13][14] The project advises that vendors apply for their own zones, so that usage patterns are easier to keep track of.[15]

References

  1. ^ IPv6 support is only partially enabled, via domain names starting with 2..[4]
  1. ^ "What the NTP Pool can offer". Retrieved April 29, 2011.
  2. ^ "pool.ntp.org: NTP Pool DNS servers". www.ntppool.org.
  3. ^ "All Pool Servers". Retrieved December 14, 2019.
  4. ^ "The time has come: we must enable IPv6 entirely". NTP Pool Project. 13 April 2021.
  5. ^ "Pool Capacity". Retrieved April 2, 2018.
  6. ^ "Reached 500 servers - Welcome Slashdot". Ask Bjørn Hansen. January 15, 2006.
  7. ^ "Yes, the pool needs more servers". Ask Bjørn Hansen. August 11, 2009.
  8. ^ "The NTP Pool needs more servers". Ask Bjørn Hansen. June 21, 2012.
  9. ^ "Public servers abuse". David L. Mills. January 21, 2003.
  10. ^ "ntp DNS round robin experiment". Adrian 'Dagurashibanipal' von Bidder. January 27, 2003.
  11. ^ "The Future is Bright, The Future is ...". Adrian 'Dagurashibanipal' von Bidder. July 24, 2005.
  12. ^ "NANOG mailing list archive: Recent NTP pool traffic increase: 2016-12-19". NANOG/opendac from shaw.ca. 2016-12-19. Archived from the original on 2017-09-24. Retrieved 2016-12-20.
  13. ^ Aleksandersen, Daniel (2017-11-23). "TP-Link repeater firmware squanders 715 MB/month". Ctrl Blog. Archived from the original on 2017-12-20. Retrieved 2017-12-21.
  14. ^ "Об инциденте с NTP-серверами" (in Russian). Yandex. 2024-11-27.
  15. ^ "pool.ntp.org: The NTP Pool for vendors". www.ntppool.org.


Stub icon

This Internet-related article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=NTP_pool&oldid=1279343810"