For many standalone Windows systems and small Active Directory environments, the NTP Pool Project provides a simple, reliable and well-supported source of accurate time.

The pool should not be thought of as a single server. It is a distributed service that changes as servers join and leave the network.

How the pool works

The NTP Pool Project uses DNS to distribute requests.

For example:

uk.pool.ntp.org

This name does not refer to one physical server. Instead, it returns addresses for suitable servers within the UK pool.

This provides several advantages:

  • Load is shared between many servers.
  • Failed servers can be removed from the pool.
  • New servers can be added without changing client configuration.
  • No individual volunteer carries all of the traffic.

Regional pools

Most administrators should use the regional pool closest to their systems.

Examples include:

uk.pool.ntp.org
us.pool.ntp.org
de.pool.ntp.org
au.pool.ntp.org

Using a regional pool normally reduces network latency while distributing traffic amongst local volunteer servers.

Configure more than one peer

Although the pool itself is distributed, Windows should still be configured with several peers.

For example:

w32tm /config /manualpeerlist:"0.uk.pool.ntp.org,0x8 1.uk.pool.ntp.org,0x8 2.uk.pool.ntp.org,0x8" /syncfromflags:manual /update

Using several peers provides resilience if one server is temporarily unavailable. Windows Time Service can evaluate the available peers rather than relying on a single source.

The numbered names are separate pool zones. Each can resolve to different servers, which gives Windows a broader selection than repeatedly querying the same unnumbered name.

Avoid mixing unrelated sources without a reason

It can be tempting to configure one server from the UK pool, one from a cloud provider and another from an organisation found in an old article.

In most ordinary Windows environments, this does not provide any useful advantage. A consistent group of well-maintained peers is generally preferable to combining unrelated sources simply for variety.

If different source types are deliberately combined, their operators, usage policies and expected availability should be understood.

Respect the volunteers

The NTP Pool Project is supported by volunteers. Most Windows environments generate very little traffic and are unlikely to cause any concern, but unusually aggressive polling should be avoided unless there is a genuine operational requirement.

If an organisation needs guaranteed service levels, very high request volumes or formal support, a commercial provider or locally hosted time service may be more appropriate.

Is the NTP Pool accurate enough?

For almost every ordinary Windows environment, the answer is yes.

Windows Time Service is not normally being used to provide sub-millisecond synchronisation across general-purpose networks. Local network conditions, virtualisation and Windows polling behaviour will often have more practical influence than the difference between reputable public NTP providers.

The NTP Pool Project is generally suitable for:

  • Standalone servers.
  • Workstations and laptops.
  • Home labs.
  • Small businesses.
  • The forest root PDC Emulator.

When should another source be used?

Another source may be more appropriate where:

  • Internet access is unreliable.
  • Time must remain accurate during WAN outages.
  • Regulatory or operational requirements specify an internal source.
  • A GPS-backed local source is available.
  • A supported commercial appliance is required.

These options are covered elsewhere in the Time Sources section.

Verify the result

After configuring Windows, always verify the selected source:

w32tm /query /source
w32tm /query /status

The configured peer list only shows what Windows has been told to use. The selected source confirms which server Windows is actually using.

Where there is doubt about connectivity, test one of the pool names directly:

w32tm /stripchart /computer:0.uk.pool.ntp.org /samples:5 /dataonly

A successful strip chart confirms that the server responds, but it does not prove that Windows has selected it as the active source.

Further information

The NTP Pool Project publishes guidance on using the service, regional pool zones, joining the pool and usage recommendations.

Visit the NTP Pool Project website

Related information