Reverse Zones Lookups for a Disjointed Namespace?

Hello, I am wondering if it is possible to do reverse lookups across two Windows domains that have a disjointed namespace?

For example, let's say client.domain1.com (192.168.1.x) needs to revolves a PTR record that exists on in a reverse zone domain2.com (1.10.10.in-addr.arpa).. Is there any way the DNS\DC (AD Integrated zone) for domain1.com could lookup a PTR record in domain2.com?

Thanks!

LVL 23
Justin DurrantSr. Engineer - Windows Server/VirtualizationAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hypercat (Deb)Commented:
If you can resolve forward lookups between the domains, then you can resolve reverse lookups.  It shouldn't be any problem at all - are you having one?  Do you have a router providing a connection between the two domains?
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
There is a router and connectivity between the domains. I am resolving forward zones just fine by using conditional forwarders. But this does not work for reverse lookups.

0
Hypercat (Deb)Commented:
What results do you get when you try a reverse lookup?  Are you sure the reverse lookup zone in domain2 is properly configured?
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
the PTR records are not found... The zone is fine because clients in domain2 have no issues.
0
Hypercat (Deb)Commented:
So, forward lookup works fine but reverse lookup doesn't.  That's weird.  Is port 53 open for TCP as well as UDP? And are you sure you need it to work?  Do you have some application that won't work without it?
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
Firewall ports are fine since my conditional forwarders work. Yes, Veritas Netback needs reverse. Current we are using HOSTS file on the NBU servers and it sucks! :)
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
Any other suggestions?
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
HELP!
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationAuthor Commented:
No one?
0
Hypercat (Deb)Commented:
JJ - did you ever try adding a static PTR entry in domain1 for the machines in domain2 that you need to resolve?  I guess you would have to add a new zone, but it might just work.  I've never heard of this, but it's worth a try, I figure...you can always delete it if it doesn't work or messes something else up.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.