|
PTR / ip6.arpa setup with BIND
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Thursday, 25 August 2005 20:58:14
I was under the impression that my BIND config was allight but PTR lookups did not seem to work.
I pretty much followed [url]http://www.fpsn.net/?pg=tools&tool=ipv6-inaddr[/url] to build my config.
I have used bold to indicate the correct lines and options {
listen-on-v6 { any; };
};
And:
// IPv6 local address
zone "a.f.0.1.8.8.8.0.1.0.0.2.ip6.arpa" {
type master;
file "2001-0888-10fa.rev";
allow-update {
none;
};
allow-query {
any;
};
allow-transfer {
any;
};
notify no;
};
And in the specific file:
$TTL 3d ; Default TTL (bind 8 needs this, bind 9 ignores it)
@ IN SOA gandalf.hugo.vanderkooij.org. whois.vanderkooij.org. (
The subnet could be coded also differently if the SOA part is correct:
$ORIGIN 0.0.0.0.a.f.0.1.8.8.8.0.1.0.0.2.ip6.arpa.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN PTR gandalf.hugo.vanderkooij.org.
2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 IN PTR aragorn.hugo.vanderkooij.org.
But due to the incorrect SOA the generated $ORIGIN and PTR lines do not work. They still work if you match $ORIGIN to your netmask.
I figured it out while I wrote this message. (Which started as a question.)
I hope it will help out someone else before they start pulling out hairs.
PTR setup with BIND?
Ever tried reading the FAQ?
The last three lines will give you the answer to your problem (the answer: contact xs4all, or most likely look in the xs4all service center to configure it.
The SOA is wrong btw, it should have the form of:
@ IN SOA primary_dns_server email.domainname.tld
It works the way you did it, but it is not correct, unless you put the arpa thing also as an NS record and add a relevant A+AAAA, thus for you:
@ IN SOA gandalf.hugo.vanderkooij.org whois.vanderkooij.org
This as your sole NS seems to be gandalf, and your contact whois@vanderkooij.org.
According to:
$ dig @gandalf.hugo.vanderkooij.org a.f.0.1.8.8.8.0.1.0.0.2.ip6.arpa. axfr
the zone works for the rest though.
The output from the generator is correct. it simply added the origin, so that one doesn't have to add the 0.0.0.0, which translates to 16 bits out of the /48, because a link is a /64 and then one can easily group the data per link.
PTR setup with BIND?
Shadow Hawkins on Thursday, 25 August 2005 20:59:37
I did not read the FAQ. But the FAQ shows the same issue with a $ORIGIN which does not match the netmask and the result is a non working part in my DNS server.
I think I might have gotten it better the first time if I just copied my file for my 192.168.1.0 network and rewrote the file to IPv6 PTR style. The generator is not producing the right lines due to a rather odd SOA record.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 25 August 2005 20:56:26
Posting is only allowed when you are