DNS for AD Domains Connected by Router

Jon Jaques
Jon Jaques used Ask the Experts™
on
I have two domains, on two different subnets, one of which is a production domain running a business, the other is a development domain for building software and testing database upgrades. I've got it so that the router has these domains connected to each other, and I can ping IP addresses on the other domains in both directions, but won't I don't have is any name resolution cross domains.

I've tried adding secondary zones to DNS, but have not been able to get it to work.

Do I need to go a step further and create a trust relationship between the two domains, or is there a simpler way to get the two domain controllers to play nice?

Thanks in advance!

--Jon
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2013

Commented:
You can use conditional forwarders, stub zones, or secondary zones.  I'd go with conditional forwarding, set it up in each domain.

Domain 1 - cond forwarder for domain 2 and vice versa

Thanks

Mike

Commented:
If you dole out the IPs via DHCP, can you add the secondary DNS server as the other site's DNS?  Or, could you possibly setup each site's DNS server to point to the other server to get the other's DNS domain and info?
Top Expert 2012

Commented:
I would have to agree with Mike conditional forwarders are the way to go.

http://www.windowsnetworking.com/articles_tutorials/dns_conditional_forwarding_in_windows_server_2003.html

Make sure your router is not blocking proper ports needed.
11/26 Forrester Webinar: Savings for Enterprise

How can your organization benefit from savings just by replacing your legacy backup solutions with Acronis' #CyberProtection? Join Forrester's Joe Branca and Ryan Davis from Acronis live as they explain how you can too.

Senior Solutions Architect
Commented:
When doing name resolution, I'm guessin you're just typing the short name and not the FQDN?

try the following(just replace the server and domain with your own details):
ping server
ping server.mydomain.com

I'm expecting the first command to fail, but the second command should work.

If this is the case, then update the DNS Suffix search order on your workstations and servers.
So next time you do a short name query that is not resolved, your DNS client will then start processing the listed DNS Suffixes and test name resolution via the FQDN.

Examples of how to push DNS suffix updates.
http://support.microsoft.com/kb/275553
http://www.techrepublic.com/blog/datacenter/manage-dns-suffix-configuration-through-group-policy/2665
Jon JaquesInformation Technologist

Author

Commented:
Hmmm, I added a conditional forwarder on the subdomain, and now I've gotten to where @dvt_localboy was referring to, I can now ping FQDNs from the main domain, but not the short netbios names... Update the DNS suffixes?
Top Expert 2012

Commented:
You need to add the DNS Suffix of the other domain in your DNS suffix search list on the clients
Jon JaquesInformation Technologist

Author

Commented:
Hey, sorry it's been a while since I've revisited this, but I think that ultimately, what I need to do is to go ahead and create the trust between the two networks; won't that go ahead and make the two networks be able to talk together seemlessly, or will I still have to use the FQDNs between them?
Jon JaquesInformation Technologist

Author

Commented:
Thanks for your help! I've had to go through several rounds of updates and changes here to get things the way that I want, but it's finally all working.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial