RFC2317 issues
Kevin Darcy
kcd at daimlerchrysler.com
Sat Jun 22 00:24:17 UTC 2002
Kirk Rafferty wrote:
> Greetings,
>
> A Google Groups search on RFC2317 was a great help to understanding RFC2317
> a little better (not to mention the RFC itself), but I'm still running into
> some problems I hope somebody can help me with.
>
> I'm using Bind 8.2.3.
>
> We have been assigned a subnet of 204.144.241.64/26.
>
> My /etc/named.conf entry looks thus:
>
> -----------------------------------------
>
> zone "26/64.241.144.204.in-addr.arpa" {
> type master;
> file "db.204.144.241";
> };
>
> -----------------------------------------
>
> My (abridged) zone file looks like:
>
> ------------------------------------------------------------
> $ORIGIN 26/64.241.144.204.in-addr.arpa.
> $TTL 86400
>
> @ IN SOA hadrian.fpcc.net. hostmaster.fpcc.net. (
> 13 ; Serial
> 10800 ; Refresh after 3 hours
> 3600 ; Retry after 1 hour
> 604800 ; Expire after 1 week
> 86400 ) ; Minimum TTL of 1 day
>
> ;
> ; Name Servers
> ;
>
> @ NS ns0.fpcc.net.
> @ NS ns1.fpcc.net.
>
> 65 PTR host1.fpcc.net.
> 66 PTR host2.fpcc.net.
>
> (...)
>
> ------------------------------------------------------------
>
> The problem is that I cannot reverse-resolve. Various dig's report the
> CNAME, but I cannot actually get a reverse lookup:
>
> $ dig -x 204.144.241.65
> ...
> ;; ANSWER SECTION:
> 65.241.144.204.in-addr.arpa. 43200 IN CNAME 65.26/64.241.144.204.in-addr.arpa.
> ...
>
> $ nslookup 204.144.241.65
> Server: 192.168.0.14
> Address: 192.168.0.14#53
>
> ** server can't find 65.241.144.204.in-addr.arpa.: NXDOMAIN
>
> Any help in pointing out what I'm doing wrong would be greatly appreciated.
Looks like they aliased the names to the 26/64.241.144.204.in-addr.arpa domain, but
they delegated the 64/26.241.144.204.in-addr.arpa zone. Oops. You should ask them
which way around they'd prefer.
- Kevin
More information about the bind-users
mailing list