Forum - reverse dns :: SixXS - IPv6 Deployment & Tunnel Broker

reverse dns

Shadow Hawkins on Monday, 19 January 2004 19:25:46

I did a bind setup, to let it work with reverse dns. If i dig it localy or from a remote ipv6 host saying it has to use my ns server it works fine. In the subnet menu i entered my ipv6 ip as reverse dns server. But after a couple of days still no dns. if i do: dig @ns1.sixxs.net 6.8.3.0.8.3.8.0.1.0.0.2.ip6.int/arpa it gives me my own ipv6 dns host as authoritive nameserver. Bus when i ask a ipv6 nameserver what my reverse is, no one can tell me. Can someone tell me what i did wrong?

reverse dns

Jeroen Massar SixXS Staff

on Monday, 19 January 2004 20:16:48

You didn't do anything wrong, but the DNS servers from RIPE don't delegate some blocks anymore as by magic, that will be sorted out, they have received many complaints already.

reverse dns

Shadow Hawkins on Monday, 26 January 2004 14:04:46

is this problem already solved?

reverse dns

Jeroen Massar SixXS Staff

on Monday, 26 January 2004 16:28:16

Test it yourself and learn from it: $ dig +trace 6.8.3.0.8.3.8.0.1.0.0.2.ip6.arpa ns Notez bien that ip6.int doesn't exist on the Concepts POP and it will never either as it has been deprecated almost three years ago.

reverse dns

Carmen Sandiego on Thursday, 26 February 2004 02:33:44

how long should it take reverse dns to work after i added name servers and (hopefully) configures bind right? iivana@box:~$ dig +trace d.7.6.0.0.6.9.0.1.0.0.2.ip6.int ; <<>> DiG 9.2.1 <<>> +trace d.7.6.0.0.6.9.0.1.0.0.2.ip6.int ;; global options: printcmd . 35106 IN NS J.ROOT-SERVERS.NET. . 35106 IN NS K.ROOT-SERVERS.NET. . 35106 IN NS L.ROOT-SERVERS.NET. . 35106 IN NS M.ROOT-SERVERS.NET. . 35106 IN NS A.ROOT-SERVERS.NET. . 35106 IN NS B.ROOT-SERVERS.NET. . 35106 IN NS C.ROOT-SERVERS.NET. . 35106 IN NS D.ROOT-SERVERS.NET. . 35106 IN NS E.ROOT-SERVERS.NET. . 35106 IN NS F.ROOT-SERVERS.NET. . 35106 IN NS G.ROOT-SERVERS.NET. . 35106 IN NS H.ROOT-SERVERS.NET. . 35106 IN NS I.ROOT-SERVERS.NET. ;; Received 436 bytes from 217.30.184.162#53(217.30.184.162) in 1 ms int. 172800 IN NS NS.ISI.EDU. int. 172800 IN NS NS0.JA.NET. int. 172800 IN NS NS1.CS.UCL.AC.UK. int. 172800 IN NS NS.UU.NET. int. 172800 IN NS NS.ICANN.ORG. ;; Received 269 bytes from 192.58.128.30#53(J.ROOT-SERVERS.NET) in 51 ms 0.1.0.0.2.ip6.int. 86400 IN NS y.ip6.int. 0.1.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 0.1.0.0.2.ip6.int. 86400 IN NS ns.ripe.net. 0.1.0.0.2.ip6.int. 86400 IN NS ns.apnic.net. 0.1.0.0.2.ip6.int. 86400 IN NS rs.arin.net. 0.1.0.0.2.ip6.int. 86400 IN NS flag.ep.net. ;; Received 337 bytes from 128.9.128.127#53(NS.ISI.EDU) in 190 ms 9.0.1.0.0.2.ip6.int. 86400 IN NS sunic.sunet.se. 9.0.1.0.0.2.ip6.int. 86400 IN NS svc00.apnic.net. 9.0.1.0.0.2.ip6.int. 86400 IN NS auth03.ns.uu.net. 9.0.1.0.0.2.ip6.int. 86400 IN NS munnari.oz.au. 9.0.1.0.0.2.ip6.int. 86400 IN NS ns.ripe.net. 9.0.1.0.0.2.ip6.int. 86400 IN NS ns.apnic.net. 9.0.1.0.0.2.ip6.int. 86400 IN NS ns3.nic.fr. ;; Received 223 bytes from 3ffe:50e::1#53(y.ip6.int) in 334 ms 0.6.9.0.1.0.0.2.ip6.int. 432000 IN NS ns2.scarlet-internet.nl. 0.6.9.0.1.0.0.2.ip6.int. 432000 IN NS ns3.scarlet-internet.nl. 0.6.9.0.1.0.0.2.ip6.int. 432000 IN NS ns1.scarlet-internet.nl. ;; Received 122 bytes from 192.36.125.2#53(sunic.sunet.se) in 10 ms 6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns1.sixxs.net. 6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns2.sixxs.net. 6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns3.sixxs.net. ;; Received 112 bytes from 213.204.195.3#53(ns2.scarlet-internet.nl) in 56 ms d.7.6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns1.afraid.org. d.7.6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns2.afraid.org. ;; Received 95 bytes from 2001:838:1:1:210:dcff:fe20:7c7c#53(ns1.sixxs.net) in 81 ms d.7.6.0.0.6.9.0.1.0.0.2.ip6.int. 60 IN SOA d.7.6.0.0.6.9.0.1.0.0.2.ip6.int. hostmaster.afraid.org.d.7.6.0.0.6.9.0.1.0.0.2.ip6.int. 2860352816 86400 7200 3600000 60 ;; Received 107 bytes from 66.115.180.24#53(ns1.afraid.org) in 193 ms is there something wrong ? B-)

reverse dns

Jeroen Massar SixXS Staff

on Thursday, 26 February 2004 03:05:38

Yups, you don't know how DNS works apparently ;) Also you might want to check the other DNS threads mentioning that ip6.int is deprecated already for 2 years, not that that has anything to do with the above but oh well.

reverse dns

Carmen Sandiego on Thursday, 26 February 2004 03:16:13

yes! everything is wrong, suprise suprise =) maybe another week with google helps thanks

reverse dns

Carmen Sandiego on Thursday, 26 February 2004 06:19:19

ok..looks like i did everything wrong..i'm tired of googling and doing everything wrong. can someone help me step by step how to get reverse dns working? i have AAAA record for rotta.saatana.org 2001:960:67d::2. is that even right? please help me, i'm desperate :(

reverse dns

Carmen Sandiego on Friday, 27 February 2004 14:05:45

It's seems to resolve, yes, so it is right. However reverse dns doesn't work completely, I see your reverse with .int works, but .arpa doesn't. As you are in production space (2001::/16), you should setup the .arpa and drop the .int as it is been deprecated almost three years ago as said many times by Jeroen. ;) You may keep the .int PTR record if you want, but I'd setup the .arpa PTR too. :)

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