Cheers Markku,
it seems from Germany, everything is going smoothly.
Perhaps, again a hickup between the US and EU ipv6 routing?
On the other hand I remember, that I did have to add my ipv6 server
using the IPv6 address rather than the hostname (for me, I have the same
hostname with both A and AAAA records).
Does it work if you add the IPv6 address, rather than your hostname?
Best regards,
Helge
PS: On http://www.pool.ntp.org/user/Spacy you can see, IPv4 is working
fine with hostnames (+IPv4), while IPv6 is not (yet). Only IP address is
available.
PPS: FWIW, my ntpdate and traceroute result:
root@spacys:~# ntpdate -6 -q 2001:4b98:dc0:41:216:3eff:fee9:a263
server 2001:4b98:dc0:41:216:3eff:fee9:a263, stratum 3, offset -0.000131,
delay 0.04884
29 Dec 03:55:28 ntpdate[8144]: adjust time server
2001:4b98:dc0:41:216:3eff:fee9:a263 offset -0.000131 sec
root@spacys:~# traceroute6 2001:4b98:dc0:41:216:3eff:fee9:a263
traceroute to 2001:4b98:dc0:41:216:3eff:fee9:a263
(2001:4b98:dc0:41:216:3eff:fee9:a263) from 2a01:4f8:110:4443::9, 30 hops
max, 24 byte packets
1 2a01:4f8:110:4440::1 (2a01:4f8:110:4440::1) 0.732 ms 1.036 ms
0.813 ms
2 hos-tr2.juniper1.rz11.hetzner.de (2a01:4f8:0:11:2:0:11:1) 0.203 ms
0.389 ms 0.424 ms
3 core22.hetzner.de (2a01:4f8:0:3::cd) 0.49 ms 0.464 ms 0.519 ms
4 core1.hetzner.de (2a01:4f8:0:3::b1) 5.217 ms 5.104 ms 5.117 ms
5 juniper1.ffm.hetzner.de (2a01:4f8:0:3::6) 4.951 ms 5.133 ms 5.176 ms
6 g0-0-0-1.decix-core2-lux-v6.gandi.net (2001:7f8::71f1:0:1) 18.478
ms 18.137 ms 18.35 ms
7 2001:4b98:1f::c3b2:3 (2001:4b98:1f::c3b2:3) 23.711 ms 24.818 ms
23.704 ms
8 p254-dist3-d-ip6.paris.gandi.net (2001:4b98:1f::c3d3:250) 23.521
ms 25.027 ms 23.356 ms
9 * * *
Am 27/12/2013 10:34, schrieb Markku Miettinen:
Hi
I've been browsing around for a couple of days and found several
people complaining about the same thing before, but there hasn't been
any single reason for this error message:
--clip--
Invalid stratum response from XXX (Your server is in stratum ). Is
your server configured properly? Is public access allowed? If you just
restarted your ntpd, then it might still be stabilizing the
timesources - try again in 10-20 minutes.
--clap--
As far as I can tell the server looks it's responding just fine with
both IPv4 and IPv6, at least to this site:
http://keetweej.vanheusden.com/query_ntp.php Both IP versions are
using the same config and I've used it before along with very same
firewall config that I now enabled again.
Only thing I can imagine is that for some reason the IPv6 monitoring
doesn't work properly for whatever reason. Is any of you able to prove
me wrong? I'm more than happy to fix anything in my end.
And for additional information, server is located in France and feel
free to probe it at ntp.surfa.name.
Thanks in advance.
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
