-RED50 at the remote site.
-XG115 at local site.
-AD domain.
-DNS & DHCP are served by the XG. XG will use OpenDNS servers if not internal lookups.
-DNS request route on XG for local AD domain.
-DHCP on XG issues primary DNS of the local domain controller. It does not issue a secondary IP address.
-Configuration on RED is standard/split.
Problem:
We lost internet at the local site today and the remote site was completely down although their are 2 WAN connections. I am assuming that had we set a secondary DNS in the XG's DHCP of a public DNS server, the remote site would at least have had internet. Yes?
My problem with that is it is an AD environment so I steer clear of public DNS servers.
What can I do to ensure this doesn't happen again but also not effect day to day AD DNS lookups.
This thread was automatically locked due to age.
