How to sort out a reverse DNS mess

%3CLINGO-SUB%20id%3D%22lingo-sub-2366631%22%20slang%3D%22en-US%22%3EHow%20to%20sort%20out%20a%20reverse%20DNS%20mess%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2366631%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EOur%20organization%20has%20a%20number%20of%2010.X.0.0%2F16%20locations%20with%20the%20same%20AD%2FDNS%20name%20ourcompany.com.%20No%20worries.%3C%2FP%3E%3CP%3EWe%20are%20connected%20to%20a%20separate%20company%20with%20the%20AD%2FDNS%20name%20othercompany.com%20who%20were%20using%20some%20172.16.XXX.0%2F22%20addresses.%20Still%20good.%3C%2FP%3E%3CP%3EWe%20used%20conditional%20forwarders%20on%20each%20companys%20DNS%20records%20to%20forward%20each%20others%20forward%20and%20reverse%20lookup%20queries%20to%20the%20other.%20Great.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20now%2C%20othercomapny.com%20is%20moving%20over%20to%2010.X.0.0%2F16%20network%20ranges.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20hit%20a%20snag%20on%20the%20ourcompany.com%20DNS%20server%20in%20that%20the%20reverse%20lookup%20zone%20is%2010.in-addr.arpa%20instead%20of%20each%20individual%20X.10.in-addr.arpa%20zone.%20This%20means%20the%20ourcompany.com%20DNS%20server%20cannot%20create%20a%20conditional%20forwarder%20for%2044.10.in-addr.arpa%20as%20this%20overlaps%20with%20our%2010.in-addr.arpa%20zone.%20As%20a%20result%20we%20cannot%20reverse%20lookup%20othercompany.com%20IP%20addresses.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDeleting%20our%20reverse%20lookup%20zone%2010.in-addr.arpa%20sounds%20pretty%20horrifying%2C%20so%20I%20am%20wondering%20is%20there%20a%20best%20approach%20to%20doing%20this%3F%20Is%20it%20possible%20at%20all%3F%3C%2FP%3E%3CP%3EI%20appreciate%20any%20advice%20anyone%20can%20give.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2366631%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDNS%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Regular Visitor

Hi,

Our organization has a number of 10.X.0.0/16 locations with the same AD/DNS name ourcompany.com. No worries.

We are connected to a separate company with the AD/DNS name othercompany.com who were using some 172.16.XXX.0/22 addresses. Still good.

We used conditional forwarders on each companys DNS records to forward each others forward and reverse lookup queries to the other. Great.

 

But now, othercomapny.com is moving over to 10.X.0.0/16 network ranges.

 

We have hit a snag on the ourcompany.com DNS server in that the reverse lookup zone is 10.in-addr.arpa instead of each individual X.10.in-addr.arpa zone. This means the ourcompany.com DNS server cannot create a conditional forwarder for 44.10.in-addr.arpa as this overlaps with our 10.in-addr.arpa zone. As a result we cannot reverse lookup othercompany.com IP addresses.

 

Deleting our reverse lookup zone 10.in-addr.arpa sounds pretty horrifying, so I am wondering is there a best approach to doing this? Is it possible at all?

I appreciate any advice anyone can give.

0 Replies
www.000webhost.com