SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #1613921
Ticket Status: Resolved

PoP: 

dns0.easynet.be not delegating 3.0.8.f.6.0.1.0.0.2.ip6.arpa
[be] Shadow Hawkins on Friday, 30 April 2010 15:24:20
This issue has already been reported (and marked as "resolved") several times in the past, first time in 2008, but it is still ongoing. Reverse DNS delegation of ranges from bebru01 (particularly 3.0.8.f.6.0.1.0.0.2.ip6.arpa) does not work through dns0.easynet.be. We have: 8.f.6.0.1.0.0.2.ip6.arpa. 172800 IN NS ns.ripe.net. 8.f.6.0.1.0.0.2.ip6.arpa. 172800 IN NS ns.easybone.net. 8.f.6.0.1.0.0.2.ip6.arpa. 172800 IN NS ns.easynet.de. 8.f.6.0.1.0.0.2.ip6.arpa. 172800 IN NS dns0.easynet.be. 8.f.6.0.1.0.0.2.ip6.arpa. 172800 IN NS ns2.easynet.net. The other NS'es delegate to ns*.sixxs.net correctly, but dns0.easynet.be returns NXDOMAIN. This makes roughly 20% of PTR lookups for these IP's fail, this is *very annoying* (try "dig +trace -x 2001:6f8:3a7::1" several times). Can either dns0.easynet.be's configuration be corrected OR can it be removed altogether from the 8.f.6.0.1.0.0.2.ip6.arpa. zone? Thanks.
State change: worksforme Locked
[ch] Jeroen Massar SixXS Staff on Friday, 30 April 2010 19:30:19
Message is Locked
The state of this ticket has been changed to worksforme
dns0.easynet.be not delegating 3.0.8.f.6.0.1.0.0.2.ip6.arpa
[ch] Jeroen Massar SixXS Staff on Friday, 30 April 2010 19:34:41
Works for me since it was resolved a long time ago; and we test several times a day if all DNS servers in the whole tree delegate down-wards properly, but there might have been some strange glitch somewhere though which might go unnoticed. See output below that it works, can you repeat that if you think that DNS server is an issue?
jeroen@bliss:~$ dig @dns0.easynet.be. 3.0.8.f.6.0.1.0.0.2.ip6.arpa ns ; <<>> DiG 9.5.1-P3 <<>> @dns0.easynet.be. 3.0.8.f.6.0.1.0.0.2.ip6.arpa ns ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11642 ;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;3.0.8.f.6.0.1.0.0.2.ip6.arpa. IN NS ;; ANSWER SECTION: 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 86400 IN NS ns3.sixxs.net. 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 86400 IN NS ns1.sixxs.net. 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 86400 IN NS ns2.sixxs.net. ;; Query time: 39 msec ;; SERVER: 212.100.160.53#53(212.100.160.53) ;; WHEN: Fri Apr 30 19:29:50 2010 ;; MSG SIZE rcvd: 109
dns0.easynet.be not delegating 3.0.8.f.6.0.1.0.0.2.ip6.arpa
[be] Shadow Hawkins on Wednesday, 05 May 2010 09:32:10
It seems to respond correctly only to explicit NS queries for the 3.0.8.f.6.0.1.0.0.2.ip6.arpa. zone (like the one you showed), but it does not delegate to those NS'es when querying for any PTR records within that zone, it returns NXDOMAIN instead: boris:ghen(0) % dig -x 2001:6f8:3a7::1 @dns0.easynet.be. ; <<>> DiG 9.5.2-P2 <<>> -x 2001:6f8:3a7::1 @dns0.easynet.be. ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50416 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.a.3.0.8.f.6.0.1.0.0.2.ip6.arpa. IN PTR ;; AUTHORITY SECTION: 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 86400 IN SOA dns0.easynet.be. hostmaster.be.easynet.net. 2008111801 28000 7200 864000 86400 ;; Query time: 24 msec ;; SERVER: 212.100.160.53#53(212.100.160.53) ;; WHEN: Wed May 5 09:25:40 2010 ;; MSG SIZE rcvd: 166 Whereas the other NS'es delegate properly, eg.: boris:ghen(0) % dig -x 2001:6f8:3a7::1 @ns.ripe.net. ; <<>> DiG 9.5.2-P2 <<>> -x 2001:6f8:3a7::1 @ns.ripe.net. ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3080 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.7.a.3.0.8.f.6.0.1.0.0.2.ip6.arpa. IN PTR ;; AUTHORITY SECTION: 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 43200 IN NS ns2.sixxs.net. 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 43200 IN NS ns3.sixxs.net. 3.0.8.f.6.0.1.0.0.2.ip6.arpa. 43200 IN NS ns1.sixxs.net. ;; Query time: 44 msec ;; SERVER: 2001:610:240:0:53::193#53(2001:610:240:0:53::193) ;; WHEN: Wed May 5 09:26:00 2010 ;; MSG SIZE rcvd: 153 Can you reproduce this?
dns0.easynet.be not delegating 3.0.8.f.6.0.1.0.0.2.ip6.arpa
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 May 2010 13:37:48
That is strange indeed. Seems there is some inconsistency there. I'll ask the Easynet folks to have a close look at it.
State change: reopened Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 May 2010 13:37:08
Message is Locked
The state of this ticket has been changed to reopened
dns0.easynet.be not delegating 3.0.8.f.6.0.1.0.0.2.ip6.arpa
[be] Shadow Hawkins on Thursday, 16 December 2010 21:43:50
The issue seems fixed ?
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Friday, 17 December 2010 12:23:14
Message is Locked
The state of this ticket has been changed to resolved

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

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