Internal DNS Problem over Site to Site VPN
Posted on 2009-04-04
I just succesfully established a site to site VPN between our main office and branch office.
The main office has two domain controllers, both running Windows Server 2003 and both are running DNS. The branch office does not have a domain controller yet but I plan to add one in the future.
The remote site is set to use one of the primary office's Domain Controllers as its DNS. External Lookups are no problem, but it can't resolve any internal FQDNs. NetBios Broadcast is enabled so I can resolve the partial name, but if I try to ping the FQDN, it tells me that the name doesn't exist. The workstations on the remote site are already joined to the domain (I did this before I moved them).
I did several nslookups and found the same thing - external domains resolve but internal hosts or the domain name (vincentlimousines.local) do not resolve.
I've chekced my VPN on both ends - it's set to allow traffic of all types between the two sites.
Any thoughts would be greatly appreciated/