SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #656591
Ticket Status: Resolved

PoP: nlede01 - BIT BV (Ede)

ns3.sixxs.net does not resolve my NS
[at] Shadow Hawkins on Saturday, 19 January 2008 18:53:08
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Hi, My SIXXS handle is: NHL1-SIXXS. A few days ago I added an NS entry for my subnet 2001:7b8:3cd::/48. It worked from the beginning. But then I saw that resolving my subnet only works sporadically. Then I noticed it works when using ns1.sixxs.net and ns2.sixxs.net but not when using ns3.sixxs.net. Here are samples with dig: When dig uses ns3.sixxs.net, there is no NS record to my server thus resolution is not working: # dig +trace 6.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. PTR ; <<>> DiG 9.3.4 <<>> +trace 6.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. PTR ;; global options: printcmd . 8677 IN NS i.root-servers.net. . 8677 IN NS j.root-servers.net. . 8677 IN NS k.root-servers.net. . 8677 IN NS l.root-servers.net. . 8677 IN NS m.root-servers.net. . 8677 IN NS a.root-servers.net. . 8677 IN NS b.root-servers.net. . 8677 IN NS c.root-servers.net. . 8677 IN NS d.root-servers.net. . 8677 IN NS e.root-servers.net. . 8677 IN NS f.root-servers.net. . 8677 IN NS g.root-servers.net. . 8677 IN NS h.root-servers.net. ;; Received 436 bytes from 192.168.200.121#53(192.168.200.121) in 2 ms ip6.arpa. 172800 IN NS NS-SEC.RIPE.NET. ip6.arpa. 172800 IN NS TINNIE.ARIN.NET. ip6.arpa. 172800 IN NS NS.ICANN.ORG. ip6.arpa. 172800 IN NS NS.LACNIC.NET. ip6.arpa. 172800 IN NS SEC1.APNIC.NET. ;; Received 220 bytes from 192.36.148.17#53(i.root-servers.net) in 38 ms 7.0.1.0.0.2.ip6.arpa. 84600 IN NS sec3.apnic.net. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS sunic.sunet.se. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS ns-pri.ripe.net. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS ns3.nic.fr. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS sec1.apnic.net. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS tinnie.arin.net. ;; Received 373 bytes from 2001:610:240:0:53::4#53(NS-SEC.RIPE.NET) in 50 ms 8.b.7.0.1.0.0.2.ip6.arpa. 172800 IN NS nsauth1.bit.nl. 8.b.7.0.1.0.0.2.ip6.arpa. 172800 IN NS nsauth2.bit.nl. 8.b.7.0.1.0.0.2.ip6.arpa. 172800 IN NS nsauth3.bit.nl. ;; Received 162 bytes from 2001:dc0:1:0:4777::140#53(sec3.apnic.net) in 448 ms 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN NS ns3.sixxs.net. 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN NS ns1.sixxs.net. 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN NS ns2.sixxs.net. ;; Received 153 bytes from 2001:7b8:3:2c::53#53(nsauth1.bit.nl) in 46 ms 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 604800 IN SOA ns1.sixxs.net. hostmaster.sixxs.net. 2008010903 10800 3600 2419200 604800 ;; Received 150 bytes from 2001:770:18:8::4#53(ns3.sixxs.net) in 130 ms On the other hand, ns2.sixxs.net answers with correct NS record, thus resolution is working: # dig +trace 6.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. PTR ; <<>> DiG 9.3.4 <<>> +trace 6.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. PTR ;; global options: printcmd . 8655 IN NS f.root-servers.net. . 8655 IN NS g.root-servers.net. . 8655 IN NS h.root-servers.net. . 8655 IN NS i.root-servers.net. . 8655 IN NS j.root-servers.net. . 8655 IN NS k.root-servers.net. . 8655 IN NS l.root-servers.net. . 8655 IN NS m.root-servers.net. . 8655 IN NS a.root-servers.net. . 8655 IN NS b.root-servers.net. . 8655 IN NS c.root-servers.net. . 8655 IN NS d.root-servers.net. . 8655 IN NS e.root-servers.net. ;; Received 436 bytes from 192.168.200.121#53(192.168.200.121) in 3 ms ip6.arpa. 172800 IN NS NS-SEC.RIPE.NET. ip6.arpa. 172800 IN NS TINNIE.ARIN.NET. ip6.arpa. 172800 IN NS NS.ICANN.ORG. ip6.arpa. 172800 IN NS NS.LACNIC.NET. ip6.arpa. 172800 IN NS SEC1.APNIC.NET. ;; Received 220 bytes from 192.5.5.241#53(f.root-servers.net) in 198 ms 7.0.1.0.0.2.ip6.arpa. 84600 IN NS ns3.nic.fr. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS sec3.apnic.net. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS sunic.sunet.se. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS ns-pri.ripe.net. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS sec1.apnic.net. 7.0.1.0.0.2.ip6.arpa. 84600 IN NS tinnie.arin.net. ;; Received 373 bytes from 2001:610:240:0:53::4#53(NS-SEC.RIPE.NET) in 49 ms 8.b.7.0.1.0.0.2.ip6.arpa. 172800 IN NS nsauth1.bit.nl. 8.b.7.0.1.0.0.2.ip6.arpa. 172800 IN NS nsauth2.bit.nl. 8.b.7.0.1.0.0.2.ip6.arpa. 172800 IN NS nsauth3.bit.nl. ;; Received 162 bytes from 2001:660:3006:1::1:1#53(ns3.nic.fr) in 72 ms 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN NS ns2.sixxs.net. 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN NS ns3.sixxs.net. 3.0.8.b.7.0.1.0.0.2.ip6.arpa. 86400 IN NS ns1.sixxs.net. ;; Received 153 bytes from 2001:7b8:3:2c::53#53(nsauth1.bit.nl) in 46 ms d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. 604800 IN NS ns1.nobaq.net. ;; Received 117 bytes from 2001:7b8:3:1e:290:27ff:fe0c:5c5e#53(ns2.sixxs.net) in 47 ms 6.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. 3600 IN PTR saugstube.ip6.nobaq.net. d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. 3600 IN NS ns1.nobaq.net. d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. 3600 IN NS ns2.nobaq.net. d.c.3.0.8.b.7.0.1.0.0.2.ip6.arpa. 3600 IN NS ns3.nobaq.net. ;; Received 229 bytes from 193.154.229.55#53(ns1.nobaq.net) in 35 ms Now it's a few days ago so I can't believe that ns3.sixxs.net is not yet updated and/or there's a negative caching with so long delay. Are there some issues with ns3.sixxs.net? Thank you very much in advance, Niki
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 19 January 2008 19:09:52
Message is Locked
The state of this ticket has been changed to resolved
ns3.sixxs.net does not resolve my NS
[ch] Jeroen Massar SixXS Staff on Saturday, 19 January 2008 19:11:21
Thanks for reporting, the DNS check scripts only run on a nightly basis thus didn't catch this yet. There is apparently a disk issue on that machine which causes it to shut down writes to the disk. Reboot made it come up again for the time being. We'll notify HEAnet to look at it.
ns3.sixxs.net does not resolve my NS
[at] Shadow Hawkins on Saturday, 19 January 2008 21:16:58
Thank you very much, works now :-)
ns3.sixxs.net does not resolve my NS
[fi] Carmen Sandiego on Sunday, 24 February 2008 12:12:24
I appear to be having the same issue with the reverse nameserver delegation for my subnet R6184 (NIC handle TJM1-SIXXS). I added the nameserver records roughly 12 hours ago, and both ns1 and ns2 provide the correct response, but ns3 still serves up a SOA record with the serial 2008021701, and doesn't return my nameservers. terom@zapotekII:~$ dig @ns3.sixxs.net -x 2001:14b8:197:1234:217:31ff:feb2:a769 ; <<>> DiG 9.3.4 <<>> @ns3.sixxs.net -x 2001:14b8:197:1234:217:31ff:feb2:a769 ; (2 servers found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10932 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;9.6.7.a.2.b.e.f.f.f.1.3.7.1.2.0.4.3.2.1.7.9.1.0.8.b.4.1.1.0.0.2.ip6.arpa. IN PTR ;; AUTHORITY SECTION: 1.0.8.b.4.1.1.0.0.2.ip6.arpa. 604800 IN SOA ns1.sixxs.net. hostmaster.sixxs.net. 2008021701 10800 3600 2419200 604800 ;; Query time: 56 msec ;; SERVER: 2001:770:18:8::4#53(2001:770:18:8::4) ;; WHEN: Sun Feb 24 13:08:41 2008 ;; MSG SIZE rcvd: 150
ns3.sixxs.net does not resolve my NS
[ch] Jeroen Massar SixXS Staff on Sunday, 24 February 2008 14:17:43
The disk issues still exist and as such zone updates are not directly processed, the new host is mostly ready though and should be replacing the current one during the coming week.

Please note Posting is only allowed when you are logged in.
Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker