SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #2096965
Ticket Status: Resolved

PoP: 

Reverse DNS delegation not operational
[us] Shadow Hawkins on Saturday, 19 June 2010 00:53:36
I setup my subnet recently, and set the reverse DNS delegation, but when I try to do a reverse lookup, the DNS servers are not delegating to my zone on the other server. Details: Subnet: 2001:1938:270::/48 Reverse DNS Delegation to: ns1.afraid.org., ns2.afraid.org., ns3.afraid.org., ns4.afraid.org. doing a "dig -x 2001:1938:270::2" returns: ;; QUESTION SECTION: ;2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.2.0.8.3.9.1.1.0.0.2.ip6.arpa. IN PTR ;; AUTHORITY SECTION: 2.0.8.3.9.1.1.0.0.2.ip6.arpa. 604800 IN SOA localhost. hostmaster.sixxs.net. 2010061302 10800 3600 2419200 604800 If I'm reading this right, the TTL on the reverse zone above my subnet is one *week*. I would have thought that adding the reverse DNS delegations would have updated the zone (including serial number, which indicates that it is last updated on June 13th using standard serial number sequencing), but it seems it has not. Will this rectify itself in a week, or is this a case of a missed serial number update on said zone, or some other issue? Thanks.
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 19 June 2010 01:35:12
Message is Locked
The state of this ticket has been changed to resolved
Reverse DNS delegation not operational
[ch] Jeroen Massar SixXS Staff on Saturday, 19 June 2010 01:35:40
Seems bind didn't want to reload new zones any more for whatever reason it had. All should be fine now.
Reverse DNS delegation not operational
[us] Shadow Hawkins on Sunday, 20 June 2010 17:20:45
I suspect that I'm having the same problem that Gavin was experiencing. I'm in the same POP has he, usphx01, and I'm seeing similar results. Perhaps, I'm not as confident that my DNS resource records are correctly formed. Locally I can resolve: # dig -x 2001:1938:243::30 ;; QUESTION SECTION: ;0.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.4.2.0.8.3.9.1.1.0.0.2.ip6.arpa. IN PTR ;; ANSWER SECTION: 0.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.4.2.0.8.3.9.1.1.0.0.2.ip6.arpa. 86400IN PTR ipv6.buici.com. ;; AUTHORITY SECTION: 3.4.2.0.8.3.9.1.1.0.0.2.ip6.arpa. 86400 IN NS ns1.buici.com. From another machine on the network, I am not seeing the expected delegation. # dig -x 2001:1938:243::30 ;; QUESTION SECTION: ;0.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.3.4.2.0.8.3.9.1.1.0.0.2.ip6.arpa. IN PTR ;; AUTHORITY SECTION: 2.0.8.3.9.1.1.0.0.2.ip6.arpa. 604800 IN SOA localhost. hostmaster.sixxs.net. 2010061702 10800 3600 2419200 604800 The serial number of the zone implies that it hasn't been updated since the 17th. I configured my rDNS delegation on the 19th. The delegation setup page states: "Do note that changes are not applied directly, as such, after a change wait a bit before checking." How long should we need to wait? Cheers
Reverse DNS delegation not operational
[ch] Jeroen Massar SixXS Staff on Monday, 21 June 2010 12:25:35
Found the problem, should now be definitely resolved, thanks for reporting. Zones should update every 15 minutes now.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker