<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<p>Sorry. It's of course from 0.at.pool.ntp.org till
3.at.pool.ntp.org <br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 16.01.25 17:26, Hans Mayer wrote:<br>
</div>
<blockquote type="cite"
cite="mid:509d17f8-0515-4ec7-90c5-a9c699603773@ma.yer.at">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<p><br>
</p>
<p>Hi Dave, <br>
</p>
<p>I am not sure if you understand how a pool is working. Or
probably it's me that I don't understand you ? <br>
If you define a pool like at.pool.ntp.org you get always 4
different IP addresses and also a different set of IP adresses.
<br>
Check it out with command "dig at.pool.ntp.org" several times. <br>
</p>
<p>For example in AT there are 4 pools from 1.at.pool.ntp.org till
4.at.pool.ntp.org <br>
So theoretically you could use the 4 from your country. ( in my
case AT is Austria ) <br>
2.at.pool.ntp.org is the only one which has IPv6 addresses too.
So if you have IPv6 too you should use a number "2" server. <br>
And the advantages of using a pool is the fact you get only
really working NTP server addresses and no dead ones. <br>
Therefore if you use some pools there is no need to change any
DNS. <br>
In the pools you get hopefully only stratum 2 servers and
higher. In 99% good enough. If you want to use a stratum 1 you
have to define it as server. And the netiquette says, one should
ask the operator if it's allowed to use it. <br>
</p>
<p>// Hans <br>
</p>
<p>-- <br>
</p>
<p><br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 16.01.25 17:04, Dave Hall via
users wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPg_kBbnU_FZ2hkv0ikT801bpcAdkWMYBTRyUYhZrjz6U0CXBQ@mail.gmail.com">
<meta http-equiv="content-type"
content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div>Hal,</div>
<div><br>
</div>
<div>Some further updates and thoughts:</div>
<div><br>
</div>
<div>Regarding the tos minclock config line: I checked one
of my systems that's still running Debian 11 and regular
NTP. This system was quite happy with only two servers.
So my original two-maaster-server configuration was OK
(but not great) until I upgraded to NTPSEC. This is not a
complaint - just me understanding how the problem crept in
on me.</div>
<div><br>
</div>
<div>Regarding the number of local masters: I completely
understand why 4 is a realistic minimum. Now that this
has been pointed out to me I will plan to move back to 4
or more in the very near future. Last night, due to
other pressing issues, I just needed to get my clocks
synchronized without thinking about (planning for) which
additional hosts to use as masters.</div>
<div><br>
</div>
<div>Regarding my question about using a local POOL, my idea
is that I could change the pool membership via DNS without
having to touch a config file on each system. So a pool
of 2 servers does seem pointless, but when I add 3 or 4
more it will be easy.</div>
<div><br>
</div>
<div>-Dave</div>
<div><br>
</div>
<div>
<div dir="ltr" class="gmail_signature">
<div dir="ltr">
<div>--</div>
<div>Dave Hall<br>
Binghamton University<br>
<a href="mailto:kdhall@binghamton.edu"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">kdhall@binghamton.edu</a><br>
</div>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Wed, Jan 15, 2025 at
10:31 PM Hal Murray <<a
href="mailto:halmurray@sonic.net" moz-do-not-send="true"
class="moz-txt-link-freetext">halmurray@sonic.net</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
> One last question: What does it take to define a
POOL? Is it just a DNS<br>
> name that resolves to more than one IP, or is there
something more? <br>
<br>
The general idea is that there are many servers in the
pool and there is <br>
some smarts behind the DNS server that will rotate through
the servers to <br>
spread the load (maybe not equally) and will monitor the
available servers <br>
and not use any that are not responding or have a clock
that is way off <br>
(aka broken).<br>
<br>
More info here:<br>
<a href="https://www.ntppool.org/en/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.ntppool.org/en/</a><br>
<br>
The client side will try again later when it wants more
servers and toss <br>
out a server from the pool when it stops responding.<br>
<br>
If you look in your log files, you will probably find lots
of clutter.<br>
<br>
In your case, with only 2 servers in the pool, I would use
2 server lines <br>
rather than the pool.<br>
<br>
<br>
-- <br>
These are my opinions. I hate spam.<br>
<br>
<br>
<br>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre wrap="" class="moz-quote-pre">_______________________________________________
users mailing list
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:users@ntpsec.org" moz-do-not-send="true">users@ntpsec.org</a>
<a class="moz-txt-link-freetext"
href="https://lists.ntpsec.org/mailman/listinfo/users"
moz-do-not-send="true">https://lists.ntpsec.org/mailman/listinfo/users</a>
</pre>
</blockquote>
</blockquote>
</body>
</html>