Problems with Reverse Lookup

[Kevin Darcy]

Two things:

1) You overqualified the owner of the zone's NS record. Since it is the
123.168.192.in-addr.arpa zone, you must have at least one NS record for
123.168.192.in-addr.arpa. Instead, you have only an NS record for
5.123.168.192.in-addr.arpa. named interprets this as the delegation of a subzone,
which is probably not what you wanted. Actually, named should have rejected the
whole zone for the absence of an NS record for itself. Didn't you see something
like that in the logs?

2) You're missing a trailing period in the PTR record's owner name, so named is
interpreting it as a PTR with an owner name of (get ready for
it) 5.123.168.192.in-addr.arpa.123.168.192.in-addr.arpa.


- Kevin

rostiguy at callisma.com wrote:

> Hello,
>
> I'm having a problem with DNS on my RedHat Linux 6.2 box.  My
> named.conf and 192.168.123 files look as such:
>
> -----name.conf-----------------------------------------------------------
> // Config file for caching only name server
>
> options {
>         directory "/var/named";
>         // Uncommenting this might help if you have to go through a
>         // firewall and things are not working out. But you probably
>         // need to talk to your firewall admin.
>         // query.source port 53;
>
>         // forward first;
>         forwarders {
>            24.91.0.66;
>            24.91.0.70;
>         };
> };
>
> zone "." {
>         type hint;
>         file "db.cache";
> };
>
> zone "0.0.127.in.addr.arpa" {
>         type master;
>         file "primaryzones/127.0.0";
> };
>
> zone "123.168.192.in.addr.arpa" {
>         notify no;
>         type master;
>         file "primaryzones/192.168.123";
> };
>
> zone "ostiguynet.com" {
>         notify no;
>         type master;
>         file "primaryzones/ostiguynet.com";
> };
> -----192.168.123 file----------------------------------------------------------
>
> 123.168.192.in-addr.arpa.       IN      SOA
> thunderheart.ostiguynet.com. rostiguy.ostiguynet.com. (
>                                                 1  ; Serial
>                                                 8H ; Refresh
>                                                 2H ; Retry
>                                                 4W ; Expire
>                                                 1D) ; Minimum TTL
> ;
> ;  Name Server Records
> ;
> 5.123.168.192.in-addr.arpa.     IN      NS
> thunderheart.ostiguynet.com.
> ;
> ;  Pointer records
> ;
> 5.123.168.192.in-addr.arpa      IN      PTR
> thunderheart.ostiguynet.com.
>
> when I do a dig an nslookup (or DIG) it appears to be working
> correctly except for resverse lookups.  When I try to resolve
> 192.168.123.5 I get the standard "Non-existent host/domain.  I have
> searched the newsgroups, tried all of the suggestions, and still no
> luck.  I'm sure it's something really stupid, but I can't seem to find
> it.
>
> Any help would be greatly appreciated...Thanks in advance.  More files
> are available upon request.
>
> Thanks,
> Ron Ostiguy
> rostiguy at mediaone.net