|
reverse DNS error
![[de]](/s/countries/de.gif) Shadow Hawkins on Tuesday, 11 March 2003 14:47:37
Hi
i have created a dns server with a reverse zone and i allways get the reply, when i try to ping the host:
64 bytes from unused.ca-range.ipv6.eurocyber.net: icmp_seq=1 ttl=64 time=0.051 ms
64 bytes from unused.ca-range.ipv6.eurocyber.net: icmp_seq=2 ttl=64 time=0.056 ms
i have a subnet and further i installed ipng which works with the dns settings and it resolved.
i hope someone could help me.
sorry for the bad english. i'm german.
mfg tobias besse
reverse DNS error
![[fi]](/s/countries/fi.gif) Shadow Hawkins on Tuesday, 11 March 2003 18:00:22
Where's the problem or error? :)
furhermore, I've had some problems updating my reversezone, IPng transfers the zone 4 time a day, but the PTR records won't update on ns1.ipng.nl. The old ones stays, but new ones won't get there.
reverse DNS error
Learn to type the records correctly.
Dig your own box yourself and see if it makes any sense.
Odd records or wrong records get filtered out automatically...
reverse DNS error
Shadow Hawkins on Thursday, 13 March 2003 15:13:44
i dont't know if the reverse service is working at the moment because all settings in my bind are right. syslog doenst show any erros. so i think i did everything right, but it resolve no hosts. i put SixXs.Dusk.eu.org on an ipv6 IP and it cannot be resolved. Have anybody tested it?
i hope that anyone could help me. thx Tobias Besse
reverse DNS error
Shadow Hawkins on Thursday, 13 March 2003 21:40:27
I have a tunnel & subnet through Cybercomm and reverse delegations don't
seem to be working for me either.
I noticed there were some problems reported last month on IPng mailing list,
but don't know if it's the same thing.
Meanwhile, lets keep dig(1)'ing ^^
reverse DNS error
Shadow Hawkins on Thursday, 13 March 2003 23:44:15
SOA query on my subnet is now correct.
Thanks invisible forces.
reverse DNS error
Nothing has changed in that setup as far as I am aware of.
SOA date is also still 20030119...
As you mention dig's could have shown what/where went wrong if at all anything was wrong.
reverse DNS error
Shadow Hawkins on Wednesday, 26 March 2003 18:59:26
Hidy Kalle,
I've got the same problem.
Do you now know what the problem was?
Greetinx, Tobias
reverse DNS error
You might dump some dig's to show what exactly is in error.
Note also that for RIR space (2001::/16) there is both ip6.arpa and ip6.int.
Some services/resolvers still depend on ip6.int.
reverse DNS error
![[si]](/s/countries/si.gif) Carmen Sandiego on Tuesday, 08 April 2003 18:10:09
Hm I also can't get reverse dns to work. If i dig up my Ipv6 subnet
(2001:960:60e::/48) I get this :
linuxdog root # dig ns e.0.6.0.0.6.9.0.1.0.0.2.ip6.int
; <<>> DiG 9.2.2 <<>> ns e.0.6.0.0.6.9.0.1.0.0.2.ip6.int
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50116
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;e.0.6.0.0.6.9.0.1.0.0.2.ip6.int. IN NS
;; AUTHORITY SECTION:
6.0.0.6.9.0.1.0.0.2.ip6.int. 10800 IN SOA ns1.sixxs.net. hostmaster.sixxs.net. 2003032501 10800 3600 2419200 604800
;; Query time: 333 msec
;; SERVER: 193.2.1.66#53(193.2.1.66)
;; WHEN: Tue Apr 8 18:08:21 2003
;; MSG SIZE rcvd: 109
And I have added ns.thedge.de and ns1.thedge.de to my subnet settings some while ago ... When will it be delegated to my dns ?
reverse DNS error
You might want to read the FAQ which clearly states that updates might take some time, we are not going to reload the DNS servers every 3 seconds or so :)
reverse DNS error
Carmen Sandiego on Saturday, 12 April 2003 13:12:33
Oki, I fixed it ;) The problem was in my reverse zonefile configuration ... Then I made zonefiles with help of this site : http://tools.fpsn.net/ipv6-inaddr/ .. Works now like a charm .
reverse DNS error
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Sunday, 27 July 2003 04:04:19
Hello,
I am having a problem with reverse DNS on my prefix from ipng, 3ffe:8114:2000:a20::/60
I have made no changes on my end for quite some time but all off a sudden my reverse dns entries are no longer working.
I checked my bind log and i am still transfering my zone file to ipng every day.
Any idea what the problem could be ?
Thanks,
Stefan Rodenburg
reverse DNS error
You might want and try to use 'dig' to show us where the error is supposed to be.
reverse DNS error
Shadow Hawkins on Thursday, 07 August 2003 10:29:33
I also seem to have trouble getting the reverse delegation to work. I have added the correct delegation 2 months ago (I persume the nameservers will get updated a few time in that timespan). The only thing is the dns reguest still aren't delegated to me; while the dns-server, which is default in my network, does do the resolving correctly...
Wouter
reverse DNS error
_what_ exactly doesn't work as it does work.
Could you show some debug output that it doesn't work ?
reverse DNS error
Shadow Hawkins on Thursday, 07 August 2003 15:42:47
I'm sorry for not being a bit more clear; the thing that goes wrong is that the SOA record doesn't point to my nameserver (ns.telox.net). In my local network reverse lookups do work because they have ns.telox.net as default server but the rest of the world cannot as there is no pointer to my ns. I hope this clearifice things a bit.
Wouter
Edit: you can try for yourself by trying to reverse resolv 2001:960:60a::1 using your default ns and than try it again by querying for the same address at ns.telox.net
reverse DNS error
I still see no debug output of you proving that it is going wrong and where what is going wrong.
For what it is worth it I can tell you that it reverses to cerberus.telox.net.
(And that is a 'global' query as you'd like to call it; in both spaces for that matter)
What exactly is wrong? (Use the dig :) )
SixXS doesn't mess with the SOA record delegated to you so even if it would be something remotely near that it would be your fault.
reverse DNS error
Shadow Hawkins on Thursday, 07 August 2003 17:03:34
Ok here is some debug information:
# First query ns.telox.net (which is my default)
localhost$ dig -n -x 2001:960:60a::1
; <<>> DiG 9.2.1 <<>> -n -x 2001:960:60a::1
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5698
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. IN PTR
;; ANSWER SECTION:
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. 86400 IN PTR cerberus.telox.net.
;; AUTHORITY SECTION:
a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. 86400 IN NS ns.telox.net.
;; Query time: 142 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Aug 7 16:58:15 2003
;; MSG SIZE rcvd: 138
*****************************************
#now query ns1.sixxs.net for a reverse lookup
localhost$ dig @ns1.sixxs.net -n -x 2001:960:60a::1
; <<>> DiG 9.2.1 <<>> @ns1.sixxs.net -n -x 2001:960:60a::1
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62130
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. IN PTR
;; Query time: 75 msec
;; SERVER: 2001:838:1:1:210:dcff:fe20:7c7c#53(ns1.sixxs.net)
;; WHEN: Thu Aug 7 16:59:58 2003
;; MSG SIZE rcvd: 89
What goes wrong is that ns1.sixxs.net isn't able to performe the reverse lookup...
Wouter
reverse DNS error
Since when does a nameserver need to be authoritive, do recursion and caching for a zone delegated to your nameserver? The IPng POP's reverses for the subnets _are_ mirrored onto ns2.sixxs.net. But that isn't true for the other POP's.
Also you might want to start using ip6.arpa. The ip6.int nameservers are not that stable you can check that quite easily with the +trace option ;)
FYI:
dig @ns1.sixxs.net 6.0.0.6.9.0.1.0.0.2.ip6.int axfr | grep telox
a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns.telox.net.
dig @ns2.sixxs.net 6.0.0.6.9.0.1.0.0.2.ip6.int axfr | grep telox
a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns.telox.net.
dig @ns3.sixxs.net 6.0.0.6.9.0.1.0.0.2.ip6.int axfr | grep telox
a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns.telox.net.
reverse DNS error
Shadow Hawkins on Thursday, 07 August 2003 18:44:41
Your digs look fine, but could you explain these:
---------
}*-> dig @ns1.sixxs.net a.0.6.0.0.6.9.0.1.0.0.2.ip6.int ns [~]
; <<>> DiG 9.2.2 <<>> @ns1.sixxs.net a.0.6.0.0.6.9.0.1.0.0.2.ip6.int ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33326
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. IN NS
;; Query time: 32 msec
;; SERVER: 2001:838:1:1:210:dcff:fe20:7c7c#53(ns1.sixxs.net)
;; WHEN: Thu Aug 7 18:38:32 2003
;; MSG SIZE rcvd: 49
---------
}*-> dig @ns2.sixxs.net a.0.6.0.0.6.9.0.1.0.0.2.ip6.int ns [~]
; <<>> DiG 9.2.2 <<>> @ns2.sixxs.net a.0.6.0.0.6.9.0.1.0.0.2.ip6.int ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1229
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. IN NS
;; AUTHORITY SECTION:
a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. 604800 IN NS ns.telox.net.
;; Query time: 30 msec
;; SERVER: 2001:7b8:3:1e:290:27ff:fe0c:5c5e#53(ns2.sixxs.net)
;; WHEN: Thu Aug 7 18:38:40 2003
;; MSG SIZE rcvd: 75
-----
}*-> dig @ns3.sixxs.net a.0.6.0.0.6.9.0.1.0.0.2.ip6.int ns [~]
; <<>> DiG 9.2.2 <<>> @ns3.sixxs.net a.0.6.0.0.6.9.0.1.0.0.2.ip6.int ns
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17740
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;a.0.6.0.0.6.9.0.1.0.0.2.ip6.int. IN NS
;; Query time: 51 msec
;; SERVER: 2001:770:18:2:201:3ff:fe2c:960c#53(ns3.sixxs.net)
;; WHEN: Thu Aug 7 18:39:00 2003
;; MSG SIZE rcvd: 49
-----
It seems that only ns2 gives the correct redirection to the telox nameserver. Which is weird afaik, but maybe there is good explanation for this behaviour :)
reverse DNS error
See the previous message and the thing about 'recursion and caching'.
reverse DNS error
Shadow Hawkins on Friday, 08 August 2003 18:45:41
Sorry, i missed the fact that no answer could also be a referral :).
The problem with my friends DNS turned out to be that the hostname in his ns record was a CNAME instead of an A and/or AAAA.
reverse DNS error
Ah, but he didn't say that his reverse to forward and back check mapping didn't work otherwise I would have mentioned that directly :)
Too bad there isn't any 'hide a future answer' option...
|
![[ch]](/s/countries/ch.gif)
on Saturday, 12 April 2003 02:08:38
Posting is only allowed when you are