ntpd appears to work with ipv6 servers, but not ipv4

by GeoSword   Last Updated June 22, 2016 08:00 AM

So, we have an ntp server (ntp-4.2.8-r1) which uses this list of time servers:

server pool.ntp.org
server 24.56.178.140 
server 2001:470:0:2c8::2
server ntp.markyate.net
server ntpv6.dianacht.de
server 127.127.1.0

However, when I use ntpq to list peers:

mns0c log # ntpq -pn 127.0.0.1
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 24.56.178.140   .INIT.          16 u    -  512    0    0.000    0.000   0.000
*2001:470:0:2c8: .CDMA.           1 u   44   64  377   80.066    6.970   0.534
 127.127.1.0     .LOCL.          10 l    -   64    0    0.000    0.000   0.000
 129.250.35.250  .INIT.          16 u    -  512    0    0.000    0.000   0.000
+2001:4d48:ad51: 193.190.230.65   2 u   48   64  377   34.838    7.614   0.850
+2001:4d88:1ffa: 193.190.230.65   2 u   47   64  377   96.723  -27.702   0.812
mns0c log # 

You can see that non of the ipv4 addresses are contactable.

This is further confirmed by a tcpdump. (I see two UDP packets leaving, but non coming back)

However, If I try using ntpdate -q <peer> I get a response! ( I know it won't actually affect my clock)

However, if I try ntpq -pn <peer> I do not get a response:

24.56.178.140: timed out, nothing received
***Request timed out

Any help greatly appreciated

Tags : ip ntp ntpd


Related Questions


ntpd: servers stuck on .INIT

Updated May 02, 2015 21:00 PM

NTP Server peering

Updated October 10, 2015 07:00 AM

Things to consider when running public NTP servers

Updated February 25, 2017 02:00 AM