Sum Wum
asked on
Problems with DNS and DC at another location
Hi,
I have some trouble with our DNS-servers and DC's.
We have two locations (A and B). Location A contains 3 DC/DNS servers and this is the primary location. Location B has 1 RODC/DNS and is our secondary site. These two locations are connected through a VPN tunnel.
When users from location A travels to location B and start up their laptop, they can't connect to any servers at location A and when I run the command "echo %logonserver%" I can see that they connect to a DC at location A.
I can ping all the servers at location A from the laptop at location B by IP, but not with the FQDN.
When I run a NSLOOKUP at location B against a server at location A, it gives me the FQDN and IP for the server. The DNS-servername is unknown though, but it gives me the IP of the DNS server at location B.
What is wrong?? :)
I have some trouble with our DNS-servers and DC's.
We have two locations (A and B). Location A contains 3 DC/DNS servers and this is the primary location. Location B has 1 RODC/DNS and is our secondary site. These two locations are connected through a VPN tunnel.
When users from location A travels to location B and start up their laptop, they can't connect to any servers at location A and when I run the command "echo %logonserver%" I can see that they connect to a DC at location A.
I can ping all the servers at location A from the laptop at location B by IP, but not with the FQDN.
When I run a NSLOOKUP at location B against a server at location A, it gives me the FQDN and IP for the server. The DNS-servername is unknown though, but it gives me the IP of the DNS server at location B.
What is wrong?? :)
Have you run any nslookup queries against your RODC? If it's an AD-integrated zone, run repadmin /showrepl and verify the zone has been replicated successfully.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
how it the DNS server in site B setup?
is it just part of the DNS zone.
check the recursive test on it to make sure that it can resolve name.
you can then enable debugging on there to to start seeing any error on the DNS lookups