We have two facilities. Each facility has its own LAN, AD and domain. Between the two facilities is a VPN connection.
I want the facility A's users to see the facility B's hosts so I manually created a Forward Zone in the facility A's DNS server. That has been working fine for long. But it's been a pain since I have to manually maintain the new/old records from time to time.
An idea recently came to my mind: why not just add the facility B's DNS server's IP address into the facility A's computers' DNS Server Address list in the way like:
DNS Server Addresses: (in facility A's computers)
10.10.10.15 (the facility A's DNS server)
10.10.50.121 (the facility B's DNS server)
10.10.10.16 (the facility A's 2nd DNS server)
10.10.50.122 (facility B's 2nd DNS server)
I assumed that in facility A, while trying to resolve B's host name, (of course 10.10.10.15 cannot resolve it,) it would pass over to the next 10.10.50.121 in the list for help. And of course the 10.10.50.121 would be able to resolve it since it is a facility B's DNS server.
Well, I found my assumption is not working. But why isn't it working? Did I miss anything?
Do you think I still need to go back to manually add and maintain a Forward Zone in facility A for resolving B's host names?