Red the other posts neither of the close ones helped, and I am sure I am just overlooking something but we are moving and I have a temp server setup at the new location running CentOS5, bind.

Forward is working fine, reverse is not, so if someone see's something I missed, feel free to point, laugh, whatever! We have a /26, so the named.conf shows;

named.conf
zone "128-192.125.101.38.in-addr.arpa" {
type master;
file "/var/named/named.128-192.125.101.38.in-addr.arpa";
};

named.128-192.125.101.38.in-addr.arpa

$TTL 2D
@ IN SOA ns1.company.com. support.company.com. (
2007081310 ; serial
7200 ; refresh
3600 ; retry
3600000 ; expire
86400 ; default_ttl
)
@ IN NS ns1.company.com.

$ORIGIN 125.101.38.in-addr.arpa.
129 IN PTR gateway-cg.company.com.
130 IN PTR static-cg-130.company.com.


As you can see we have .128-192. I tried a few things nothing helped. I am testing by both a dig -x and an nslookup, so that's where I am at.

Thanks for all info.

Your config and zone file look fine, but the problem is that almost all reverse DNS is handled by your ISP. Generally if you need public reverse DNS lookup for your servers, this must be handled by the ISP's DNS servers, since they are authoritative for their their slice of in-addr.arpa pie and root DNS servers have no clue about your reverse zone file.

Thanks, our ISP does have the server IP to pass on the requests, but regardless, shouldn't that answer to himself?

If I do an nslookup <enter>
server = that servers ip <enter>
Address: 38.101.125.131#53
38.101.125.174 <enter>

** server can't find 174.125.101.38.in-addr.arpa: NXDOMAIN

Shouldn't that bypass any ISP etc. as I am telling NSlookup what server to use?

Tnx again

Yes, it should. Check /var/log/messages to see if BIND is reporting any errors loading the zone file.

Hey, look at that;
Jan 30 03:44:48 named[16615]: /var/named/named.128-192.125.101.38.in-addr.arpa:77: ignoring out-of-zone data (174.125.101.38.in-addr.arpa)

That could be a good start. I looked around and from the examples, it looks right! I tried to keep it short for testing, just not sure why it's saying it's out of zone. I redid the zone a bit and put one IP in one line so it looks like this;

174.125.101.38.in-addr.arpa. IN PTR cs0.testing.com.

Restarted and got;
Jan 30 04:29:08 named[16960]: /var/named/named.128-192.125.101.38.in-addr.arpa:13: ignoring out-of-zone data (174.125.101.38.in-addr.arpa)
Jan 30 04:29:08 named[16960]: zone 128-192.125.101.38.in-addr.arpa/IN: loaded serial 2007081312

and an nslookup test shows;
** server can't find 174.125.101.38.in-addr.arpa: NXDOMAIN

Thanks for any ideas / errors you may see.

I just saw it. Missed it before :-( It's the zone record in named.conf:

zone "128-192.125.101.38.in-addr.arpa" {
type master;
file "/var/named/named.128-192.125.101.38.in-addr.arpa";
};

should be:

zone "125.101.38.in-addr.arpa" {
type master;
file "/var/named/named.128-192.125.101.38.in-addr.arpa";
};

The in-addr.arpa domain dates back to the early (and I'm talking EARLY) days of TCP/IP and does understand classless subnetting. It expects all domain boundaries to be on strict Class A, B, and C subnets, so you can't do a partial subnet in the in-addr.arpa zone file.

Try that. It will probably work.

That did it.

Thanks so much for keeping up with the thread. Once thread's get that 3/4 replies, people don't just jump to read, but I do appreciate you keeping up and solving.

Have a good one'

Lance