Forum - reverse deligations problem / update time? :: SixXS

reverse deligations problem / update time?

Carmen Sandiego on Friday, 09 July 2004 13:50:40

Good day to you Yesterday i added one more reverse ns deligation to my /48 tunnel. By this the other deligations stopped working. root@gateway root # host -t ptr `ipv6calc -r 2001:6f8:1246::1` No input type specified, try autodetection...found type: ipv6addr Host 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.6.4.2.1.8.f.6.0.1.0.0.2.ip6.int not found: 2(SERVFAIL) All other reverses output a SERVFAIL too. So i thought there will be a update time until the changes are made? - So today i was checking it, and still the same. How long will that take? Or did i made a mistake? Thanks.

reverse deligations problem / update time?

Jeroen Massar SixXS Staff

on Friday, 09 July 2004 13:59:04

Check 'dig +trace' as mentioned in the FAQ a couple of times.

reverse deligations problem / update time?

Carmen Sandiego on Monday, 12 July 2004 20:36:15

Well i've a second problem - now my reverse works but only half a part. My Problem is: some nameservers can resolve my reverse, others cant, on some i get SERVFAIL - thats really stupid. I dont know anymore what it might be. I've reverses for IP 2001:6f8:1246::5 till 2001:6f8:1246::9. I used host(x) and dig - like dig -t ptr `ipv6calc -r 2001:6f8:1246::5` @specific_server. Some Servers can resolve this others just output a SERVFAIL. I really dont know i'll put both reverse zones - arpa and int online. Hope that someone can tell me what's that damn wrong about 'em. http://www.xeper.ath.cx/files/reverse-_48.IP6.ARPA http://www.xeper.ath.cx/files/reverse-_48.IP6.INT From here all zones are working correctly. From some other persons too - i test it but not at all. Something has to be wrong, but since im quite new to this DNS stuff, my knowledge is limitated. I tried to google and searched in Forums like the one on www.ipv6-net.de - i saw that my problem is not unheard of. Though, still i was not able to fix it. I thank anyone who try to help me - at the moment im kinda pissed off about this stuff. I really, hate this pseudo errors |:( Ps.: The forward is on another machine, and it works correctly - but this doesnt affect the reverse, right?

reverse deligations problem / update time?

Jeroen Massar SixXS Staff

on Tuesday, 13 July 2004 09:12:10

The "dig -t ptr -r" options are bogus, sometimes they do ip6.int sometimes ip6.arpa depending on version of dig and also who build and maybe patched it. Any output of that? Did you do a dig +trace ? I guess not... if you did you would see: 6.4.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 604800 IN NS ns1.xeper.ath.cx. ;; Received 80 bytes from 2001:770:18:8::2#53(ns3.sixxs.net) in 29 ms 6.4.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 259200 IN NS ns1.sixxs.net. 6.4.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 259200 IN NS ns1.xeper.ath.cx. 6.4.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 259200 IN NS ns2.sixxs.net. 6.4.2.1.8.f.6.0.1.0.0.2.ip6.arpa. 259200 IN NS ns3.sixxs.net. ;; Received 143 bytes from 217.226.5.51#53(ns1.xeper.ath.cx) in 86 ms ns1/2/3.sixxs.net really are not authoritive for your zone.... Funny that you hate yourself making 'pseudo errors' ;)

reverse deligations problem / update time?

Carmen Sandiego on Tuesday, 13 July 2004 12:57:19

The "dig -t ptr -r" options are bogus, sometimes they do ip6.int sometimes ip6.arpa depending on version of dig and also who build and maybe patched it. Any output of that?

Would that be a problem? - i guess not if i have both arpa and int anyways. I did that already and no useful output of that.

ns1/2/3.sixxs.net really are not authoritive for your zone....

Yeah i just did that yesterday night, well was late - i tried anything already, anyways. So thats really not the point - i took them out and still SERVFAIL.

Funny that you hate yourself making 'pseudo errors'

Not really, never said so - still no one could help me why exacly this "SERVFAIL" appaers. that i put ns*.sixxs.net in the zone is not the mistake, i just did that out of less knowledge - just tried it. I'll get SERVFAIL anyways no matter. And i really dont get the issue of that - the problem is that it works on some sites but not at all. Thats the problem. And how can this be my mistake? - The zone seems to be correct. As i said "dig +trace" doesnt helps - it just says "everything is fine" - from here it works, it always resolves. But not from other sites - thats the problem. So if the sixxs.net ns's were the only mistake, then its okay now or not? - So why does it still not work?

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