The problem is the subnet already exists in both domains... -Brian
________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 11:49 AM To: NT System Admin Issues Subject: RE: DNS Reverse lookup question You can use a stub domain or a forwarding domain. Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael Link with me at: http://www.linkedin.com/in/theessentialexchange From: Webb, Brian (Corp) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2008 12:47 PM To: NT System Admin Issues Subject: DNS Reverse lookup question Here is the situation: 1 IP range has servers from 2 different domains DNS servers (AD integrated) for each domain have entries for the servers in that domain If I do a reverse lookup from a machine that is pointed to the "right" DNS server it works, otherwise I get a non-existent domain. Hw do you solve this? Do you manually put in PTR records for all the servers in the opposite domain? Example: Server1.corp.local is at 10.1.1.10 Server2.division.local is at 10.1.1.20 Client1.corp.local is at 10.100.100.100 with DNS server pointed to DNSserver.corp.local Client2.division.local is at 10.200.200.200 with DNS server pointed to DNSserver.division.local nslookup from client1 for 10.1.1.10 returns Server1 nslookup from client1 for 10.1.1.20 returns non-existent domain nslookup from Client2 for 10.1.1.10 returns non-existent domain nslookup from Client2 for 10.1.1.20 returns Server2 nslookup by name (forward lookup) works everywhere. Brian Webb - MCSE TDS Corporate IS, Windows Server Platform Team Senior Systems Administrator "When stuck on a problem as often can be, try to remember G.B.T.T.D. (Go Back To The Definition)". - Dave Seybold ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
