non-glue record below bottom of zone (whoops)
Mathias Körber
mathias at koerber.org
Thu Feb 1 09:47:40 UTC 2001
> my 129.128.73.198.209.in-addr.arpa file looks like this
I think that file should be called 128.73.198.209.in-addr.arpa.. (no 129!)
> ----------------------------------
> $include named.soa 128.73.198.209.in-addr.arpa.
I don't thik you'd need the second field here, and you can also lose
the $ORIGIN below, as long as this zone is names 129.73.198.209.in-addr.arpa in
your named.conf..
>
> $ORIGIN 128.73.198.209.in-addr.arpa.
>
> @ IN NS digifix.digifix.com.
>
> 129 IN NS digifix.digifix.com.
> 129 IN NS ns.blacksmith.com.
Why do you delegate yet another sub-zone? I don;t think this is necessary..
After all, you put all the PTR records into this file..
>
In short, you should have:
in named.conf:
-------------
...
zone "128.73.198.209.in-addr.apra" IN {
type master;
file "128.73.198.209.in-addr.arpa";
...
};
and in 128.73.198.209.in-addr.arpa:
--------------------------------
$include named.soa
@ IN NS digifix.digifix.com.
IN NS ns.blacksmith.com.
129 IN PTR ....
...
That is all that should be required from you. Your ISP would have
to publish the CNAMES from 129.73.198.209.in-addr.arpa to 129.128.73.198.209.in-addr.arpa.
HTH HAND
More information about the bind-users
mailing list