Ticket ID: SIXXS #10650978 Ticket Status: Resolved PoP: sesto01 - Availo (Stockholm)
ns2.sixxs.net returns different results than ns1/3.
Shadow Hawkins on Monday, 09 December 2013 07:56:22
Hi,
2.2.5.8.0.0.f.f.8.d.6.1.1.0.0.2.ip6.arpa returns different result on ns1/3 vs ns2.sixxs.net:
$ dig ns 2.2.5.8.0.0.f.f.8.d.6.1.1.0.0.2.ip6.arpa @ns1.sixxs.net
...
;; AUTHORITY SECTION:
2.2.5.8.0.0.f.f.8.d.6.1.1.0.0.2.ip6.arpa. 14400IN NS ns.0x63.nu.
...
whereas:
$ dig ns 2.2.5.8.0.0.f.f.8.d.6.1.1.0.0.2.ip6.arpa @ns2.sixxs.net
...
;; AUTHORITY SECTION:
8.0.0.f.f.8.d.6.1.1.0.0.2.ip6.arpa. 14400 IN SOA localhost. hostmaster.sixxs.net. 2013111602 10800 3600 2419200 14400
thanks,
Anders
ns2.sixxs.net returns different results than ns1/3.
Jeroen Massar on Monday, 09 December 2013 09:32:19
You saw the difference between a host that did update and one which was still processing the new updates.
Unfortunately, DNSSEC is quite a heavy burden on DNS servers and updates thus tend to take a bit to reload.
Posting is only allowed when you are logged in. |