Question Locked

DNS issues establishing a trust between domains

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Help me out tech republic? I'm trying to establish a trust between two domains in different forests. I've created a secondary zone in forward lookup on both domains and allowed zone transfers to the opposite domain external IP address on each domain's primary zone record. My issue is I can't seem to get the trust created because there is some problem with dns talking across the domains to the other domain. I can ping the external address from each domain to the opposite domain, but I can't get a ping back from the opposite domain's internal address. When I ping the domain name, it returns the internal address as the destination of the ping, but won't send any replys back. When I ping the domain controller fQDN on the opposite domain, it does the same, shows the internal IP of the server but won't send a reply. In all my troubleshooting, I think the reason for this could be something on my firewalls blocking the internal address from being mapped to the external address to come across the domains. I'm just not sure what it could be. I can't establish the trust because the domains can't see each other despite dns having all the records. Please advise if you have any ideas.

5 replies

by wizard-09

I had the same issue as you, i created LMHOST files to resolve the issue below is a sample of my lmhost file.

***.***.*.** EXSERVER #PRE #DOM:EXHIBFS.LOCAL
***.***.*.** "EXHIBFS.LOCAL \0x1b" #PRE

How to create LMHOST files

http://support.microsoft.com/kb/180094

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome.

by tgillette

I'm still having trouble here. I've got two domain controllers in two different forests. Both domains are Server 2003, with forest and domain functional levels at 2003 levels. Both domains are on seperate private networks at seperate physical locations. Each location is connected to the internet via dsl, and each has an untangle firewall box between the internet router and the DC. They have different external IP addresses for the internet connection and the same internal subnet on both ends. I'm trying to get a forest trust relationship established between the two forests, but the problem I'm having is while DNS gets the secondary zone transfers in forward lookup zones on both sides, it's not communicating across to the opposite domain controller server to establish the trust. It errors out and says the new domain trust wizard cannot complete because the domain cannot be contacted. I can ping the gateways and external address of each domain, but can't seem to get through to the private IP and server name to establish the trust.I've got port forwarding set on both ends for port 53 tcp and udp, and I think it could be a issue with the firewall setups, but I really have run out of ideas on how to establish this trust. If anyone out there has dealt with this sort of scenario, I'm open to suggestions and ideas on how to solve it. Thank you.
Trevor Gillette

by wizard-09

I have said above use lmhost files for this as it's much easier, I completed my 3 domain trusts using the lmhost google lmhost files

by churdoo

The first problem is, if site A is resolving site B to its PRIVATE IP, that CAN'T by definition route across the public internet. PRIVATE IP's are private BY DEFINITION, and have no way in your current setup to route to the opposite site's external IP / untangle box.

I think even if you populate LMHOSTS as t_mcnally suggests (forcing the domains to resolve to their respective PUBLIC IP's), that will solve part of the problem, but you don't have the forwarding in place to make a successful trust relationship, and if you DID put the correct forwarding in place, you'd expose your servers to things from the public internet you don't want them exposed to.

Therefore, I think you need to create a site-site VPN first by
a) re-IP one site so it's PRIVATE IP's are different than the other (this is required for site-site VPN). So if site A is 10.10.11.0/24 for example, make site B 10.10.12.0/24 or whatever, but the private networks have to be DIFFERENT
b) create a site-site VPN between your two untangle boxes.

With the sites on different private networks and VPN in place, your sites will be able to resolve and route to their respective private IP's through the VPN tunnel, without compromising your network security. Oh and you might as well remove that DNS port forward (port 53) cuz you won't need it any more.

Hope this helps; post back more questions if you need to.
--C

This discussion is closed to new replies.