Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / DNS / June 2004

Tip: Looking for answers? Try searching our database.

Reverse Lookup Across Domain DNS Servers Not Working

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nick Jordan - 30 Jun 2004 01:18 GMT
I am unsure if this problem has been addressed before. I have a DNS
reverse-lookup problem.

I have two domains, Domain A and Domain B. Domain A is a W2K
native-mode domain. Domain B is a Win NT4.0 domain. Domain A uses
AD-integrated DNS. Domain B uses a UNIX DNS server. Domain A's W2K DNS
server forwards unresolved DNS queries to Domain B's UNIX server.
Computer Comp1, IP 10.6.49.132, is in Domain A. Computer Comp2, IP
10.0.33.51, is in Domain B.

From within Domain A, the commands NSLOOKUP COMP1 and NSLOOKUP
10.6.49.132 both produce the correct results, i.e., Comp1's IP address
and Comp1's FQDN, respectively. From within Domain B, the commands
NSLOOKUP COMP2 and NSLOOKUP 10.0.33.51 both produce the correct
results, i.e., Comp2's IP address and Comp2's FQDN, respectively. In
other words, DNS lookup and DNS reverse-lookup within each domain
works OK. Also, from within Domain A, NSLOOKUP COMP2 produces the
correct result, 10.0.33.51.

Here is my problem: From within Domain A, NSLOOKUP 10.0.33.51 gives an
error message: "(Domain A's DNS server FQDN) can't find 10.0.33.51:
Non-existent domain".

In the DNS table of Domain A, under Reverse Lookup Zones, there is an
entry 10.in-addr.arpa.

What is wrong, and how can I fix this reverse lookup problem?

Thank you.

Nick
Kevin D. Goodknecht Sr. [MVP] - 30 Jun 2004 17:57 GMT
> I am unsure if this problem has been addressed before. I have a DNS
> reverse-lookup problem.
[quoted text clipped - 23 lines]
>
> What is wrong, and how can I fix this reverse lookup problem?

You have to domains and two subnets?
In this situation each reverse zone should cover only it respective subnet.
In other words if domain A's subnet is 10.0.33.x then the reverse zone
should be 33.0.10.in-addr.arpa. that will keep it fron being authoritative
over domain B's subnet.
If Domain  B's subnet is 10.6.49.x then its reverse lookup should be
49.6.10.in-addr.arpa. for the same reason as above. Then each DNS server
should have a Secondary of the other's reverse lookup zone.

The problem is now that you have only one reverse zone for both subnets that
covers every IP you have.

Or two domains and one subnet?
If you only have one subnet, then one DNS server should have a primary zone
and the other should have one secondary zone.

Signature

Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group"  via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.