|
documentation problem about ntp? ntp.eu.sixxs.net vs eu.ntp.sixxs.net
![[fr]](/s/countries/fr.gif) Shadow Hawkins on Saturday, 11 June 2011 16:46:50
Greetings,
The page https://www.sixxs.net/tools/ntp refers to ntp.eu.sixxs.net, but the actual DNS name seems to be eu.ntp.sixxs.net as seen below:
$ /usr/ports/net/ntp> host ntp.eu.sixxs.net
Host ntp.eu.sixxs.net not found: 3(NXDOMAIN)
$ /usr/ports/net/ntp> host eu.ntp.sixxs.net
;; Truncated, retrying in TCP mode.
eu.ntp.sixxs.net has address 78.35.24.124
eu.ntp.sixxs.net has address 78.141.179.38
...
eu.ntp.sixxs.net has IPv6 address 2001:648:2ffc:1106::2
eu.ntp.sixxs.net has IPv6 address 2001:6a0:1:1::2
eu.ntp.sixxs.net has IPv6 address 2001:6f8:200:1003::10
...
same for ap.ntp.sixxs.net and us.ntp.sixxs.net.
Should be a simple change to the HTML page.
Regards,
Denis F. (dfr4-sixxs.net)
documentation problem about ntp? ntp.eu.sixxs.net vs eu.ntp.sixxs.net
Don't use nslookup for troubleshooting DNS, use dig.
The ntp.{us|eu|ap}.sixxs.net labels are correct, though they actually live somewhere else.
There seems to be a problem with BIND-based recursors which fail to follow the CNAME/NS combo.
To demo that it works fine using a apparently non-bind recursor (aka the google public dns):
dig @8.8.8.8 ntp.us.sixxs.net
; <<>> DiG 9.7.3 <<>> @8.8.8.8 ntp.us.sixxs.net
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22253
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ntp.us.sixxs.net.INA
;; ANSWER SECTION:
ntp.us.sixxs.net.2163INCNAMEus.ntp.sixxs.net.
us.ntp.sixxs.net.86400INA66.223.254.250
us.ntp.sixxs.net.86400INA201.48.254.14
us.ntp.sixxs.net.86400INA209.197.5.66
us.ntp.sixxs.net.86400INA209.197.16.66
us.ntp.sixxs.net.86400INA216.93.250.26
|
![[ch]](/s/countries/ch.gif)
on Monday, 13 June 2011 00:09:40
Posting is only allowed when you are