DNS between two separate domains

I have two separate domains right now that can ping each other by IP address but not by hostnames. Temporarily I need DNS to work for these two domains. How would I go about setting that up?
I tried creating new zones but I can't get the two to talk using hostnames.

One is a 2008 environment and the other is a 2003 environment.
LVL 3
WinsoupAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
DrDave242Connect With a Mentor Commented:
Conditional forwarders or stub zones are the preferred methods of providing DNS resolution between domains. They go about it in different ways, but from the client perspective, the results are the same: machines in one domain can resolve FQDNs in the other.

Let us know if you need assistance configuring either one.
0
 
KorbusConnect With a Mentor Commented:
I'm NOT positive on this, lets see if other experts agree:  Configure the primary forwarders on each DNS server to reference the other.

I'm assuming these two DNS servers are on the same LAN.  If not please let us know, it may be firewall\routing\networking issues presenting comm.
0
 
MaheshConnect With a Mentor ArchitectCommented:
Try below

You may use GPO \ registry \ manual method to add DNS suffix search list of opposite domains in network card properties \ advanced \ DNS tab of required machines at both end

Note that 1st domain in the list must be client own domain followed by other \ opposite domain, other wise client own domain name resolution and authentication will break

GPO setting "DNS Suffix search list" can be found under
Computer configuration\administrative templates\Network\Dns Client

Note that domain names must be entered one by one separated by comma with 1st domain of client own (Very IMP) without inverted comma

This will enable you DNS name resolution for another domain host names as well
Client will query 1st its own domain for record, if not found it will search another domain in list and it will resolve it if found

Note that in order to find another domain, on both domain DNS servers you must specify conditional forwarder \ secondary zones for opposite side domain pointing to its domain controller

Also note that TCP port 53 must be opened between both side domain controllers bi-directional in order to make this work

Mahesh.
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
WinsoupAuthor Commented:
I'll try these suggestions and get back to you guys on how it goes.
0
 
WinsoupAuthor Commented:
When I ping the domain name that I am trying to reach I get back an IP address of their old mail server which is not in use anymore.
Also when I added their DC to our DNS server as a forwarder it says that it's not authoritative, but it is. Will just deleting the entry for the old mail server take care of this or is there a way to tell it what the authoritative server is?
0
 
DrDave242Connect With a Mentor Commented:
I've seen the "not authoritative" thing before when adding a conditional forwarder, even though the server I was adding was indeed authoritative. In my case, name resolution still worked fine, so I think it's just a glitch.

When I ping the domain name that I am trying to reach I get back an IP address of their old mail server which is not in use anymore.
There's probably a blank host record with that IP address on their DNS server. If that server isn't in use anymore, the record should be deleted. Blank host records in an AD domain should only be used to designate domain controllers.
0
 
WinsoupAuthor Commented:
It's all working now. Getting rid of those old records cleaned up the last of the issues I had.
Thank you all for the suggestions.
0
All Courses

From novice to tech pro — start learning today.