reverse delegation problem

Email Archive archive at securityinsight.com
Wed Mar 22 00:05:07 UTC 2000


Folks,

I am having some problems delegating the reverse dns for a subnetted
class C to another dns server. The servers that are primary for
205.183.255.x are proxy.xpeditesystems.com (205.183.255.6) and
ns1.xpedite.com (137.236.4.7) [a secondary].  

I am trying to delegate 205.183.255.224-254 to
medns1.messagereach.com (205.183.255.229) and medns2.messagereach.com
(205.183.255.231) [a secondary].

The proxy and ns1 systems are running bind 4.9.4-P1 and 4.9.3-P1
respectivily.  The medns1 & 2 systems are running bind 8.2.2-P5

In the proxy's named.boot file I have
----------------------------------------------------------------------

primary 255.183.205.IN-ADDR.ARPA. db.xpeditesystems.rev

----------------------------------------------------------------------
In the db.xpeditesystems.rev  file on the proxy I have.
----------------------------------------------------------------------

224.255.183.205.in-addr.arpa. IN CNAME
224.224-254.255.183.205.in-addr.arpa.
225.255.183.205.in-addr.arpa. IN CNAME
225.224-254.255.183.205.in-addr.arpa.
... continuing until
254.255.183.205.in-addr.arpa. IN CNAME
254.224-254.255.183.205.in-addr.arpa.

224-254.255.183.205.in-addr.arpa. 3600 IN NS medns1.messagereach.com.
224-254.255.183.205.in-addr.arpa. 3600 IN NS medns2.messagereach.com.

-----------------------------------------------------------------------
In the medns1.messagereach.com named.conf file (same in medns2) I have.
-----------------------------------------------------------------------

zone "224-254.255.183.205.IN-ADDR.ARPA" in {
        type master;
        file "db.205.183.255.224-254";
};

---------------------------------------------------------------------
In the db.205.183.255.224-254 file on medns1.messagereach.com I have.
---------------------------------------------------------------------

$TTL 3600
@ IN  SOA medns1.messagereach.com. hostmaster.messagereach.com.

                        ( 7 10800 3600 604800 3600 )

                                IN  NS  medns1.messagereach.com.
                                IN  NS  medns2.messagereach.com.

229   IN  PTR   medns1.messagereach.com.
231   IN  PTR   medns2.messagereach.com.
227   IN  PTR   memailin1.messagereach.com.
232   IN  PTR   memailin2.messagereach.com.
228   IN  PTR   mewww1.messagereach.com.
235   IN  PTR   mewww2.messagereach.com.
226   IN  PTR   memailout1.messagereach.com.
233   IN  PTR   memailout2.messagereach.com.
234   IN  PTR   memailout3.messagereach.com.
236   IN  PTR   memailout4.messagereach.com.
230   IN  PTR   pull1.messagereach.com.
237   IN  PTR   pull2.messagereach.com.
--------------------------------------------------------------------

I think I have done everything right.. at least accoridng to the dns&bind
book ver 3.

When I go to the proxy and try to do a nslookup on 205.183.255.237
or any other ip listed above it seems to work fine.

When I try from medns1&2 for the same ip address it fails with this
error..

root at medns1 # nslookup 205.183.255.237
*** Can't find server name for address 205.183.255.229: Server failed

I end up just timing out on everwhere else on the net that I tried it. 

Any ideas?

--------------------------------------------------------------------
One other minor issue I am having is that on the medns1 and 2 boxes
I keep getting this error message in the logs when bind is restarted.
What should I do to resolve this?

Mar 21 18:38:54 medns1 named[9108]: check_hints: no A records for
L.ROOT-SERVERS.NET class 1 in hints

Thanks a LOT! Mike








More information about the bind-users mailing list