Reverse DNS lookup problem

[gw1500se]

This is driving me nuts and I need some new eyes to figure out what I’m doing wrong. I have several subnets that are set up for reverse lookup. One is not working but for the life of me I cannot see what is wrong. The file loads on the master with no errors, however, when I attempt to look up addresses on that subnet, I get the SRVFAIL error. In addition, the ‘named’ log has a ‘Lame server’ error for that lookup. Can someone give me some ideas as to how to debug this? TIA.

[sciron]

Can you post your zone file and your zone definition in named.conf?

[gw1500se]

Thanks for the reply. I don’t see any reason why not, its all public anyway.

Here’s the named.conf entry:
[code]
zone “128-26.55.158.72.in-addr.arpa” IN {
type master;
file “db.72.158.55.dev”;
};
[/code]
Here’s the zone file ‘db.72.158.55.dev’:
[code]
$TTL 86400
128-26.55.158.72.in-addr.arpa. IN SOA xserveoda.55.158.72.in-addr.arpa. support.aimaudit.com. (
2006052504 ; serial
2H ; refresh
2H ; retry
1W ; expiry
1D ) ; minimum
; nameservers

128-26.55.158.72.in-addr.arpa. IN NS ns2.cl.bellsouth.net.
128-26.55.158.72.in-addr.arpa. IN NS ns3.cl.bellsouth.net.
128-26.55.158.72.in-addr.arpa. IN NS xserveobd.aimaudit.com.
128-26.55.158.72.in-addr.arpa. IN NS xservetwo.aimaudit.com.
128-26.55.158.72.in-addr.arpa. IN NS xserveone.aimaudit.biz.

;hosts

130 IN PTR ImageONE-RAID.dev.aimaudit.com.
131 IN PTR aimwebserver.dev.aimaudit.com.
132 IN PTR 4dserverxp.dev.aimaudit.com.
133 IN PTR aimdlink1.dev.aimaudit.com.
134 IN PTR xraidc1.dev.aimaudit.com.
[/code]

[sciron]

Potentionally some issues.
For starters, ‘named-checkzone’ and ‘named-checkconf’ can be handy tools, but do NOT rely on them religiously. And yes, they are included with OSX.
The .conf portion has an issue. It reads:
zone “128-26.55.158.72.in-addr.arpa” IN {
type master;
file “db.72.158.55.dev”;
};

It should read:

zone “55.158.72.in-addr.arpa” {
type master;
file “db.55.158.72.dev”;
};

The reasons being are:
1) IN can be omitted MOST places with Bind, you are not doing Chaosnet resolution are you?
2) the stuff between quotes after ‘zone’ MUST BE A PROPER reverse lookup zone. I must assume from your example that 72.158.55.0/24 is your network segment. This gets complicated in a minute if this is a public server and a public zone.
if your network segment for the zone is 192.168.1.0/24, you MUST SPECIFY the reverse zone in proper notation: 1.168.192.in-addr.arpa. It looks like you mixed some definitions up back up there.

Bind does NOT like empty lines in zone files. This may be platform specific, but it has been my exeperience with Bind in the x86 world that it pukes (not to mention its mentioned in the Bind documentation). Use ; for comments on those blank lines.
Next, your SOA definition is stated incorrectly. You have:
128-26.55.158.72.in-addr.arpa. IN SOA xserveoda.55.158.72.in-addr.arpa. support.aimaudit.com. (
2006052504 ; serial
2H ; refresh
2H ; retry
1W ; expiry
1D ) ; minimum

Which should be
@ IN SOA xserveoda.aimaudit.com. support.aimaudit.com. ( bleh )

The @ just simplifies things, Bind replaces @ with the zone name. You MUST SPECIFY your domain name server IN FORWARD NOTATION, not reverse.

; nameservers

128-26.55.158.72.in-addr.arpa. IN NS ns2.cl.bellsouth.net.
128-26.55.158.72.in-addr.arpa. IN NS ns3.cl.bellsouth.net.
128-26.55.158.72.in-addr.arpa. IN NS xserveobd.aimaudit.com.
128-26.55.158.72.in-addr.arpa. IN NS xservetwo.aimaudit.com.
128-26.55.158.72.in-addr.arpa. IN NS xserveone.aimaudit.biz.

****USE FORWARDERS for the above, it simplifies things unless you are doing zone transfers. It also allows for more customization later.

;hosts

130 IN PTR ImageONE-RAID.dev.aimaudit.com.
131 IN PTR aimwebserver.dev.aimaudit.com.
132 IN PTR 4dserverxp.dev.aimaudit.com.
133 IN PTR aimdlink1.dev.aimaudit.com.
134 IN PTR xraidc1.dev.aimaudit.com.

Hope it helps, bind can be a pita.

[Author]

Posts