Jennifer1024
asked on
Main site to remote site DNS problem via VPN tunnel
This weekend my Data Center was moved from one location to another. The old location is now a branch office of the new location. All the servers are at the main location, domain, dns, dhcp ect. The only thing that remains at the branch location is a ASA firewall, switch and some thin clients. A vpn tunnel was created between the ASA at the main and the ASA at the remote. The remote site is getting DHCP addresses from the ASA and the main site is getting DHCP from the DHCP server. The addresses are not the same.
Ideally, I want both sites to get all of the DHCP and DNS information from the main site. Is that possible and if so how?
If that isnt possible can I configure my DNS servers to resolve the hostnames from the branch sites ip addressing scheme?
We go live in the morning so help is much appreciated as soon as possible!
Ideally, I want both sites to get all of the DHCP and DNS information from the main site. Is that possible and if so how?
If that isnt possible can I configure my DNS servers to resolve the hostnames from the branch sites ip addressing scheme?
We go live in the morning so help is much appreciated as soon as possible!
ASKER
There isn't a server at the remote site. Just a switch and the ASA. Right not neither site can really talk to the other as the addresses are not being resolved.
OK. So modify the DHCP server in the ASA firewall to point clients DNS to the main site and manage DNS stuff from there. I'd still leave the remote clients getting addresses from the local firewall.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I modified the DHCP server on the remote ASA to point DNS queries to my DNS servers at the main. I also set up DHCP relay to my DHCP servers. So far I'm not seeing any difference and the ARP table on the remote ASA still shows old addresses.
ASKER
Update: I forged ahead with different IP addresses at the remote site. Many of these clients are connecting through thin clients or can connect with RDP so that works fine. They can connect to the TS at the main site without any issues. However, I'm having a hard time printing from the TS server back to the remote sites printers. The printers have new addresses as well and install fine on the server but no luck there either.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
One thing to keep in mind, though, is the scope. If you have many sites, remote sites confgured the same way, you'll want to ensure that each issues different addresses.
The main reason for leaving the address issued locally is to eliminate the need to allow broadcast traffic across the VPN (DHCP requests are a boradcast)