|
1 | 1 | [% page.title = 'How do I setup NTP to use the pool?' %]
|
2 | 2 |
|
3 | 3 | <div class="block">
|
4 |
| - <h3 id="use">How do I use pool.ntp.org?</h3> |
5 |
| - |
6 |
| - <p> |
7 |
| - If you just want to synchronise your computers clock to the network, the configuration file (for the ntpd program from the <a href="http://www.ntp.org">ntp.org distribution</a>, on any supported operating system - <b>Linux, *BSD, Windows and even some more exotic systems</b>) is really simple: |
8 |
| - </p> |
9 |
| - |
10 |
| - [% INCLUDE "ntppool/use/sample-config.html" %] |
11 |
| - |
12 |
| - <p> |
13 |
| - The 0, 1, 2 and 3.pool.ntp.org names point to a random set of servers that will |
14 |
| - change every hour. Make sure your computer's clock is set to something |
15 |
| - sensible (within a few minutes of the 'true' time) - you could use <code>ntpdate |
16 |
| - 2.pool.ntp.org</code>, or you could just use the <code>date</code> command and set it |
17 |
| - to your wristwatch. Start ntpd, and after some time (this could take as long as |
18 |
| - half an hour!), <code>ntpq -pn</code> should output something like: |
19 |
| - </p> |
20 |
| - |
21 |
| - [% INCLUDE "ntppool/use/sample-pool-ntpq.html" %] |
22 |
| - |
23 |
| - <p> |
24 |
| - The IP addresses will be different, because you've been assigned random |
25 |
| - timeservers. The essential thing is that one of the lines starts with an |
26 |
| - asterisk (<code>*</code>), this means your computer gets the time from the internet |
27 |
| - - you'll never have to worry about it again! |
28 |
| - </p> |
29 |
| - <p>On more recent Linux operating systems, time setting has been delegated to |
30 |
| - <code>systemd</code>. You can use <code>timedatectl</code> to set the time: |
31 |
| - </p> |
32 |
| - |
33 |
| - [% INCLUDE "ntppool/use/sample-timedatectl.html" %] |
34 |
| - |
35 |
| - <p> |
36 |
| - On RedHat et al. (Fedora, CentOS, etc.) <a href="https://chrony.tuxfamily.org/"><code>chronyd</code></a> |
37 |
| - has replaced <code>ntpd</code> as the default NTP client (and server). With respect |
38 |
| - to the time source configuration it uses the same syntax as <code>ntpd</code>, |
39 |
| - so you can use the example above. Usually, the shipped configuration comes with a |
40 |
| - a sensible default using the distribution's vendor pool and doesn't need any adjusting at all. |
41 |
| - For checking on the synchronization status, use <code>chronyc -n sources</code>. |
42 |
| - The output is similar to <code>ntpq</code> including the asterisk designating |
43 |
| - the current time source. |
44 |
| - </p> |
45 |
| - <p> On older systems, <code>ntpd</code> may not support the pool configuration described |
46 |
| - above. The following should work with legacy <code>ntpd</code> versions: |
47 |
| - </p> |
48 |
| - |
49 |
| - [% INCLUDE "ntppool/use/sample-ntpq.html" %] |
50 |
| - |
51 |
| - <p> |
52 |
| - Looking up <code>2.pool.ntp.org</code> (or <code>0.pool.ntp.org</code>, |
53 |
| - <code>1.pool.ntp.org</code>, etc) will usually return IP addresses for servers |
54 |
| - in or close to your country. For most users this will give the best results.<br> |
55 |
| - <strong>Note:</strong> For historical reasons only <code>2.pool.ntp.org</code> will |
56 |
| - return both IPv4 <emphasize>and</emphasize> IPv6 addresses. The other names only |
57 |
| - return IPv4 addresses. |
58 |
| - </p> |
59 |
| - |
60 |
| - <p>You can also use the <a href="/zone/@">continental zones</a> (For example |
61 |
| - <a href="/zone/europe">europe</a>, |
62 |
| - <a href="/zone/north-america">north-america</a>, |
63 |
| - <a href="/zone/oceania">oceania</a> |
64 |
| - or <a href="/zone/asia">asia</a>.pool.ntp.org), |
65 |
| - and a country zone (like |
66 |
| - ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, |
67 |
| - 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone |
68 |
| - might not exist for your country, or might contain only one or two timeservers. |
69 |
| - </p> |
70 |
| - <p> |
71 |
| - If you're using <b>a recent Windows version</b>, you can use the ntp |
72 |
| - client that is built into the system. As administrator enter</p> |
| 4 | + <h3 id="use">How do I use pool.ntp.org?</h3> |
| 5 | + |
| 6 | + <p> |
| 7 | + If you just want to synchronise your computers clock to the network, the configuration file (for the ntpd program from the <a href="http://www.ntp.org">ntp.org distribution</a>, on any supported operating system - <b>Linux, *BSD, Windows and even some more exotic systems</b>) is really simple: |
| 8 | + </p> |
| 9 | + |
| 10 | + [% INCLUDE "ntppool/use/sample-config.html" %] |
| 11 | + |
| 12 | + <p> |
| 13 | + The 0, 1, 2 and 3.pool.ntp.org names point to a random set of servers that will |
| 14 | + change every hour. Make sure your computer's clock is set to something |
| 15 | + sensible (within a few minutes of the 'true' time) - you could use <code>ntpdate |
| 16 | + 2.pool.ntp.org</code>, or you could just use the <code>date</code> command and set it |
| 17 | + to your wristwatch. Start ntpd, and after some time (this could take as long as |
| 18 | + half an hour!), <code>ntpq -pn</code> should output something like: |
| 19 | + </p> |
| 20 | + |
| 21 | + [% INCLUDE "ntppool/use/sample-pool-ntpq.html" %] |
| 22 | + |
| 23 | + <p> |
| 24 | + The IP addresses will be different, because you've been assigned random |
| 25 | + timeservers. The essential thing is that one of the lines starts with an |
| 26 | + asterisk (<code>*</code>), this means your computer gets the time from the internet |
| 27 | + - you'll never have to worry about it again! |
| 28 | + </p> |
| 29 | + <p>On more recent Linux operating systems, time setting has been delegated to |
| 30 | + <code>systemd</code>. You can use <code>timedatectl</code> to set the time: |
| 31 | + </p> |
| 32 | + |
| 33 | + [% INCLUDE "ntppool/use/sample-timedatectl.html" %] |
| 34 | + |
| 35 | + <p> |
| 36 | + On RedHat et al. (Fedora, CentOS, etc.) <a href="https://chrony.tuxfamily.org/"><code>chronyd</code></a> |
| 37 | + has replaced <code>ntpd</code> as the default NTP client (and server). With respect |
| 38 | + to the time source configuration it uses the same syntax as <code>ntpd</code>, |
| 39 | + so you can use the example above. Usually, the shipped configuration comes with a |
| 40 | + a sensible default using the distribution's vendor pool and doesn't need any adjusting at all. |
| 41 | + For checking on the synchronization status, use <code>chronyc -n sources</code>. |
| 42 | + The output is similar to <code>ntpq</code> including the asterisk designating |
| 43 | + the current time source. |
| 44 | + </p> |
| 45 | + <p> On older systems, <code>ntpd</code> may not support the pool configuration described |
| 46 | + above. The following should work with legacy <code>ntpd</code> versions: |
| 47 | + </p> |
| 48 | + |
| 49 | + [% INCLUDE "ntppool/use/sample-ntpq.html" %] |
| 50 | + |
| 51 | + <p> |
| 52 | + Looking up <code>2.pool.ntp.org</code> (or <code>0.pool.ntp.org</code>, |
| 53 | + <code>1.pool.ntp.org</code>, etc) will usually return IP addresses for servers |
| 54 | + in or close to your country. For most users this will give the best results.<br> |
| 55 | + <strong>Note:</strong> For historical reasons only <code>2.pool.ntp.org</code> will |
| 56 | + return both IPv4 <emphasize>and</emphasize> IPv6 addresses. The other names only |
| 57 | + return IPv4 addresses. |
| 58 | + </p> |
| 59 | + |
| 60 | + <p>You can also use the <a href="/zone/@">continental zones</a> (For example |
| 61 | + <a href="/zone/europe">europe</a>, |
| 62 | + <a href="/zone/north-america">north-america</a>, |
| 63 | + <a href="/zone/oceania">oceania</a> |
| 64 | + or <a href="/zone/asia">asia</a>.pool.ntp.org), |
| 65 | + and a country zone (like |
| 66 | + ch.pool.ntp.org in Switzerland) - for all these zones, you can again use the 0, |
| 67 | + 1 or 2 prefixes, like 0.ch.pool.ntp.org. Note, however, that the country zone |
| 68 | + might not exist for your country, or might contain only one or two timeservers. |
| 69 | + </p> |
| 70 | + <p> |
| 71 | + If you're using <b>a recent Windows version</b>, you can use the ntp |
| 72 | + client that is built into the system. As administrator enter</p> |
73 | 73 | <pre class="code">
|
74 | 74 | w32tm /config /syncfromflags:manual /manualpeerlist:"2.pool.ntp.org 3.pool.ntp.org 0.pool.ntp.org 1.pool.ntp.org"
|
75 | 75 | </pre>
|
76 |
| - <p> |
77 |
| - at the command prompt. This will work on Windows 2003 and newer. If you use an |
78 |
| - older version of windows you can try</p> |
| 76 | + <p> |
| 77 | + at the command prompt. This will work on Windows 2003 and newer. If you use an |
| 78 | + older version of windows you can try</p> |
79 | 79 | <pre class="code">
|
80 | 80 | net time /setsntp:"2.pool.ntp.org 3.pool.ntp.org 0.pool.ntp.org"
|
81 | 81 | </pre>
|
82 |
| - <p> |
83 |
| - The same can be achieved by, as administrator, right-clicking the clock in the taskbar, |
84 |
| - selecting 'Adjust Date/Time' and entering the server name in the 'Internet Time' tab. |
85 |
| - </p> |
| 82 | + <p> |
| 83 | + The same can be achieved by, as administrator, right-clicking the clock in the taskbar, |
| 84 | + selecting 'Adjust Date/Time' and entering the server name in the 'Internet Time' tab. |
| 85 | + </p> |
86 | 86 |
|
87 |
| - <p> |
88 |
| - Meinberg made a port of the <a href="http://www.meinberg.de/english/sw/ntp.htm">ntp daemon for windows</a>. |
89 |
| - </p> |
| 87 | + <p> |
| 88 | + Meinberg made a port of the <a href="http://www.meinberg.de/english/sw/ntp.htm">ntp daemon for windows</a>. |
| 89 | + </p> |
90 | 90 |
|
91 |
| - <p> |
92 |
| - If your Windows system is part of a domain, you might not be able to independently update your computer time. |
| 91 | + <p> |
| 92 | + If your Windows system is part of a domain, you might not be able to independently update your computer time. |
93 | 93 |
|
94 |
| - For more information about setting the time on windows, see <a href="http://technet.microsoft.com/en-us/library/cc773013%28WS.10%29.aspx">How Windows Time Service Works</a>. |
95 |
| - </p> |
| 94 | + For more information about setting the time on windows, see <a href="http://technet.microsoft.com/en-us/library/cc773013%28WS.10%29.aspx">How Windows Time Service Works</a>. |
| 95 | + </p> |
96 | 96 | </div>
|
97 | 97 |
|
98 | 98 | <div class="block">
|
99 |
| - <h3 id="notes">Additional Notes</h3> |
100 |
| - |
101 |
| - <p><span class="hook">Consider if the NTP Pool is appropriate |
102 |
| - for your use</span>. If business, organization or human life |
103 |
| - depends on having correct time or can be harmed by it being |
104 |
| - wrong, you shouldn't "just get it off the internet". The NTP |
105 |
| - Pool is generally very high quality, but it is a service run |
106 |
| - by volunteers in their spare time. Please talk to your |
107 |
| - equipment and service vendors about getting local and reliable |
108 |
| - service setup for you. See also our <a href="/tos.html">terms |
109 |
| - of service</a>. |
110 |
| - |
111 |
| - We recommend time servers from |
112 |
| - <a href="http://www.meinbergglobal.com/english/products/ntp-time-server.htm">Meinberg</a>, |
113 |
| - but you can also find time servers from |
114 |
| - <a href="https://endruntechnologies.com/products/ntp-time-servers">End Run</a>, |
115 |
| - <a href="https://www.orolia.com/solution/timing-and-synchronization/">Orolia</a> |
116 |
| - and many others. |
117 |
| - </p> |
118 |
| - |
119 |
| - <p><span class="hook">If you have a static IP address and a reasonable Internet connection</span> (bandwidth |
120 |
| - is not so important, but it should be stable and not too highly loaded), please |
121 |
| - consider donating your server to the server pool. It doesn't cost you more than |
122 |
| - a few hundred bytes per second traffic, but you help this project survive. |
123 |
| - Please <a href="/join.html">read the joining page</a> for more information. |
124 |
| - </p> |
125 |
| - |
126 |
| - <p><span class="hook">If your Internet provider has a timeserver</span>, or if you know of a good timeserver |
127 |
| - near you, you should use that and not this list - you'll probably get better |
128 |
| - time and you'll use fewer network resources. If you know only one timeserver |
129 |
| - near you, you can of course use that and two from pool.ntp.org or so.</p> |
130 |
| - |
131 |
| - <p><span class="hook">It can rarely happen that you are assigned the same timeserver twice</span> - |
132 |
| - just restarting the ntp server usually solves this problem. If you |
133 |
| - use a country zone, please note that it may be because there is only |
134 |
| - one server known in the project - better use a continental zone in |
135 |
| - that case. You can <a href="/zone">browse the zones</a> to see how |
136 |
| - many servers we have in each zone.</p> |
137 |
| - |
138 |
| - <p><span class="hook">Be friendly</span>. Many servers are provided by volunteers, and almost all time |
139 |
| - servers are really file or mail or webservers which just happen to also run ntp. |
140 |
| - So don't use more than four time servers in your configuration, and don't play |
141 |
| - tricks with <code>burst</code> or <code>minpoll</code> - all you will gain is extra |
142 |
| - load on the volunteer time servers.</p> |
143 |
| - |
144 |
| - <p><span class="hook">Make sure that the <i>time zone configuration</i> of your computer is correct</span>. |
145 |
| - ntpd itself does not do anything about the time zones, it just uses UTC |
146 |
| - internally.</p> |
147 |
| - |
148 |
| - <p><span class="hook">If you are synchronising a network to pool.ntp.org</span>, please set up one of your |
149 |
| - computers as a time server and synchronize the other computers to that one. |
150 |
| - (you'll have some reading to do - it's not difficult though. And there's always |
151 |
| - the <a href="https://community.ntppool.org/">community</a> to help out.)</p> |
152 |
| - |
153 |
| - <p class="thanks">At this point, I'd like to thank those donating their time and timeservers to |
154 |
| - this network.</p> |
| 99 | + <h3 id="notes">Additional Notes</h3> |
| 100 | + |
| 101 | + <p><span class="hook">Consider if the NTP Pool is appropriate |
| 102 | + for your use</span>. If business, organization or human life |
| 103 | + depends on having correct time or can be harmed by it being |
| 104 | + wrong, you shouldn't "just get it off the internet". The NTP |
| 105 | + Pool is generally very high quality, but it is a service run |
| 106 | + by volunteers in their spare time. Please talk to your |
| 107 | + equipment and service vendors about getting local and reliable |
| 108 | + service setup for you. See also our <a href="/tos.html">terms |
| 109 | + of service</a>. |
| 110 | + |
| 111 | + We recommend time servers from |
| 112 | + <a href="http://www.meinbergglobal.com/english/products/ntp-time-server.htm">Meinberg</a>, |
| 113 | + but you can also find time servers from |
| 114 | + <a href="https://endruntechnologies.com/products/ntp-time-servers">End Run</a>, |
| 115 | + <a href="https://www.orolia.com/solution/timing-and-synchronization/">Orolia</a> |
| 116 | + and many others. |
| 117 | + </p> |
| 118 | + |
| 119 | + <p><span class="hook">If you have a static IP address and a reasonable Internet connection</span> (bandwidth |
| 120 | + is not so important, but it should be stable and not too highly loaded), please |
| 121 | + consider donating your server to the server pool. It doesn't cost you more than |
| 122 | + a few hundred bytes per second traffic, but you help this project survive. |
| 123 | + Please <a href="/join.html">read the joining page</a> for more information. |
| 124 | + </p> |
| 125 | + |
| 126 | + <p><span class="hook">If your Internet provider has a timeserver</span>, or if you know of a good timeserver |
| 127 | + near you, you should use that and not this list - you'll probably get better |
| 128 | + time and you'll use fewer network resources. If you know only one timeserver |
| 129 | + near you, you can of course use that and two from pool.ntp.org or so.</p> |
| 130 | + |
| 131 | + <p><span class="hook">It can rarely happen that you are assigned the same timeserver twice</span> - |
| 132 | + just restarting the ntp server usually solves this problem. If you |
| 133 | + use a country zone, please note that it may be because there is only |
| 134 | + one server known in the project - better use a continental zone in |
| 135 | + that case. You can <a href="/zone">browse the zones</a> to see how |
| 136 | + many servers we have in each zone.</p> |
| 137 | + |
| 138 | + <p><span class="hook">Be friendly</span>. Many servers are provided by volunteers, and almost all time |
| 139 | + servers are really file or mail or webservers which just happen to also run ntp. |
| 140 | + So don't use more than four time servers in your configuration, and don't play |
| 141 | + tricks with <code>burst</code> or <code>minpoll</code> - all you will gain is extra |
| 142 | + load on the volunteer time servers.</p> |
| 143 | + |
| 144 | + <p><span class="hook">Make sure that the <i>time zone configuration</i> of your computer is correct</span>. |
| 145 | + ntpd itself does not do anything about the time zones, it just uses UTC |
| 146 | + internally.</p> |
| 147 | + |
| 148 | + <p><span class="hook">If you are synchronising a network to pool.ntp.org</span>, please set up one of your |
| 149 | + computers as a time server and synchronize the other computers to that one. |
| 150 | + (you'll have some reading to do - it's not difficult though. And there's always |
| 151 | + the <a href="https://community.ntppool.org/">community</a> to help out.)</p> |
| 152 | + |
| 153 | + <p class="thanks">At this point, I'd like to thank those donating their time and timeservers to |
| 154 | + this network.</p> |
155 | 155 | </div>
|
0 commit comments