If it helps, everything seems OK from Germany:
# for X in a b c d e f g h; do echo asking $X.ntpns.org, ANSWER SECTION:;
dig +short pool.ntp.org @$X.ntpns.org; done
asking a.ntpns.org, ANSWER SECTION:
78.46.80.115
129.70.132.34
176.221.43.3
176.9.106.131
asking b.ntpns.org, ANSWER SECTION:
# ntpdate -q godzilla.empire.org
server 2001:470:8:104::2, stratum 1, offset 0.003384, delay 0.13257
server 69.25.29.12, stratum 0, offset 0.00, delay 0.0
27 Feb 14:45:42 ntpdate[9402]: adjust time server 2001:470:8:104::2 offset
0.003384 sec
it seems the ntp server is running properly
You can setup multiple servers, but only one IP is fetched from a DNS
server at a time. That's a fact of the DNS system. If IPv6 is running
properly, records are priorised. That means that every client able to
use IPv6 will use IPv6.
Am 13.03.2013 01:56 schrieb Darryl Ross dar...@afoyi.com:
2013/4/30 Jason Cipriani jason.cipri...@gmail.com
I am currently working on a project where 60 devices, all behind a router
with one WAN IP, update their time from north-america.pool.ntp.org on
boot. They all boot at the same time.
I frequently run into rate limit errors.
I am going to add
it's a firewall problem on the voip machine,
not an attack from 5.9.29.107 (my machine).
Can anyone confirm that?
Thanks in advance!
*Oliver Domke*
+49 1575 663 66 53 | m...@piflix.de | Brünestr. 69, DE-52531 Übach-Palenberg
___
pool mailing list
pool
freundlichen Grüßen,
___
Oliver Domke
oliver domke <m...@piflix.de> schrieb am Mo., 17. Okt. 2016 um 17:44 Uhr:
> Ralf Hildebrandt <ralf.hildebra...@charite.de> schrieb am Mo., 17. Okt.
> 2016 um 10:58 Uhr:
>
> > timeprotocol src_ip src_port
rning (same dest. net).
The real problem is, these addresses are not reachable (no route, testet on
hetzner, telekom, netcologne). That means the request, that causes the
answers, most likely came from another source.
As it already had stopped, I was no
