I'm using a slightly modified version of named 9.8 to manage an internal-only domain. The forward lookups are working ok but reverse isn't. There aren't any error messages - just no hostname returned.
What I've tried:
>dig hostname
- gives (what looks like) all relevant info
QUESTION, ANSWER, AUTHORITY, ADDITIONAL - all present and correct
taking the IP address from this -
>dig -x <ip address>
QUESTION and AUTHORITY only returned. No hostname
>host <hostname>
hostname <hostname> has address <ip address>
>host -a <ip address>
Trying "<reversed IP>.in-addr.arpa"
Host <reversed IP>.in-addr.arpa. not found: 3(NXDOMAIN)
Received 100 bytes from <DNS server>#53 in 4 ms
So this says my DNS server isn't responding to reverse requests.. but is to forward requests? Is there some other way to debug my named.conf
file?
NOTE: through all of this - no errors in /var/log/named.log
or /var/log/messages
.
System is running RHEL 5 (x64)
EDIT: note that dig -x <IP address not in my zone>
works fine.
All dig
commands are against the primary (and only) nameserver.
snip from named.conf
:
zone "20.10.in-addr.arpa" {
type master;
database "mysqldb named_pocl 10_20 localhost named_acct password";
allow-query { trusted-nets; };
allow-update { trusted-nets; };
allow-transfer { trusted-nets; };
notify no;
forwarders { };
};
I'm assuming that this named extension isn't returning the correct values for the reverse lookup. What I'm hoping to learn is how to determine what is missing or erroneous so I can fix it.
There are two tables with information for BIND: 'pocl' (domain name - contains 'A' records) and '10_20' (ip range - contains 'PTR' records). Each table contains an entry for every server + entries for 'NS', 'SOA', 'MX', etc.
** Looking through the source for the db connector I'm not convinced that it even supports PTR records. This might be a huge, gaping reason why it isn't working. Yikes.
10.1.2.0/24
, is there an2.1.10.in-addr.arpa
zone? If so, what does it contain?