DNS Problems

unameits
unameits used Ask the Experts™
on
I am having trouble setting up reverse DNS. MY ISP is saying they have setup everything correctly but I am getting an error when I do a dig. BAD (HORIZONTAL) REFERRAL I have two CENTOS Servers setup with 6.6 and Bind DNS. I have the reverse DNS setup on both of these dns servers and I can access everything fine when I connect directly to 64.41.186.27 or 64.41.186.28.

Please let me know if anyone has any ideas.


@8.8.8.8 -x 64.41.186.27 +trace

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 -x 64.41.186.27 +trace
; (1 server found)
;; global options: +cmd
.                  21217      IN      NS      e.root-servers.net.
.                  21217      IN      NS      j.root-servers.net.
.                  21217      IN      NS      c.root-servers.net.
.                  21217      IN      NS      l.root-servers.net.
.                  21217      IN      NS      i.root-servers.net.
.                  21217      IN      NS      b.root-servers.net.
.                  21217      IN      NS      k.root-servers.net.
.                  21217      IN      NS      h.root-servers.net.
.                  21217      IN      NS      m.root-servers.net.
.                  21217      IN      NS      g.root-servers.net.
.                  21217      IN      NS      d.root-servers.net.
.                  21217      IN      NS      a.root-servers.net.
.                  21217      IN      NS      f.root-servers.net.
;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 34 ms

in-addr.arpa.            172800      IN      NS      b.in-addr-servers.arpa.
in-addr.arpa.            172800      IN      NS      f.in-addr-servers.arpa.
in-addr.arpa.            172800      IN      NS      e.in-addr-servers.arpa.
in-addr.arpa.            172800      IN      NS      a.in-addr-servers.arpa.
in-addr.arpa.            172800      IN      NS      d.in-addr-servers.arpa.
in-addr.arpa.            172800      IN      NS      c.in-addr-servers.arpa.
;; Received 419 bytes from 202.12.27.33#53(202.12.27.33) in 173 ms

64.in-addr.arpa.      86400      IN      NS      r.arin.net.
64.in-addr.arpa.      86400      IN      NS      t.arin.net.
64.in-addr.arpa.      86400      IN      NS      u.arin.net.
64.in-addr.arpa.      86400      IN      NS      v.arin.net.
64.in-addr.arpa.      86400      IN      NS      w.arin.net.
64.in-addr.arpa.      86400      IN      NS      x.arin.net.
64.in-addr.arpa.      86400      IN      NS      y.arin.net.
64.in-addr.arpa.      86400      IN      NS      z.arin.net.
;; Received 179 bytes from 203.119.86.101#53(203.119.86.101) in 187 ms

186.41.64.in-addr.arpa.      86400      IN      NS      dns03.savvis.net.
186.41.64.in-addr.arpa.      86400      IN      NS      dns02.savvis.net.
186.41.64.in-addr.arpa.      86400      IN      NS      dns04.savvis.net.
186.41.64.in-addr.arpa.      86400      IN      NS      dns01.savvis.net.
;; Received 133 bytes from 199.71.0.63#53(199.71.0.63) in 48 ms

186.41.64.in-addr.arpa.      600      IN      NS      ns2.zooce.com.
186.41.64.in-addr.arpa.      600      IN      NS      ns1.zooce.com.
;; BAD (HORIZONTAL) REFERRAL
;; Received 88 bytes from 209.1.222.246#53(209.1.222.246) in 14 ms

27.186.41.64.in-addr.arpa. 14400 IN      PTR      ns1.zooce.com.
186.41.64.in-addr.arpa.      86400      IN      NS      ns1.zooce.com.
186.41.64.in-addr.arpa.      86400      IN      NS      ns2.zooce.com.
;; Received 134 bytes from 64.41.186.27#53(64.41.186.27) in 18 ms
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Distinguished Expert 2017

Commented:
You seem to have a block 64.41.186.24/29

There is no way they could delegate you the 186.41.64.in-addr.arpa
Commonly the delegation zone name will be the range of IPs as the last octet. In your case I guess your network ip is 64.41.186.24/29 the zone they would delegate would be
24-31.186.41.64.in-addr.arpa. In ns
In this zone, you will have
26 in PTR
27 in PTR

While on their side, they would need to have entries in the following format
In the 186.41.64.in-addr.arpa zone
26 in CNAME 26.24-31.186.41.64.in-addr.arpa.
Double check the name of the zone they delegated to you so that you can define it on your servers.
Distinguished Expert 2017

Commented:
Did you register ns1 and ns2 with their IPd through your domain registrar?

If you could clarify what exactly your issue is as it is not clear and I am trying to cover/infer/Devine what the various possible issues.

Author

Commented:
Arnold why do you say they can't delegate 186.41.64.in-addr.arpa. I have an entire C class. 64.41.186.0/24

Yes both of the name servers are registered with the domain registrar.

The problem that occurs is most of the time you can not perform a reverse DNS lookup. When I attempt to with Nslookup I get  can't find 64.41.186.25: Server failed
Distinguished Expert 2017

Commented:
They can not delegate because of the manner in which it is registered with Arin and with them.

One option you have is to subordinate the zone such that they configure their servers to slave the zone of 186.41.64.in-addr.arpa from your servers. or have them configure the 186.41.64.in-addr.arpa as a forwarder zone to your servers,

This way on your server the zone will include their name servers in addition to yours and when you make changes, their servers will be notified of the change at which point they will trigger the update.

The issue currently is that their server is returning a negative response with a reference to your servers.

This is likely the cause for your issue. a request to an authoritative server must come with an answer.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial