Page 1 of 1

Best practices? Redirect clients to second dns when main dc needs to go offline

Posted: Mon Apr 23, 2018 6:57 am
by adamlevine
I have 2 Zentyal domain controllers.

dc1 acts as main dns server, transparent DNS cache not enabled, forwarding to google root dns to resolve external addresses.

When dc1 is offline, I checked that can nslookup, set dc2 as the server and resolve both internal and external addresses, but it needs to be specified manually.

What are the best ways to automate this: router? client-side script? group policy?

Re: Best practices? Redirect clients to second dns when main dc needs to go offline

Posted: Sat Jun 23, 2018 8:12 am
by adamlevine
Hello everyone
Hello everyone
Hello everyone

Re: Best practices? Redirect clients to second dns when main dc needs to go offline

Posted: Wed Jul 04, 2018 4:42 pm
by rsenio
Why can't you specify two DNS servers. Specifying DNS is a function of DHCP, and there's a spot on the Access Server to choose an option.

DNS Settings
Pushing DNS servers to clients is optional, unless clients' Internet traffic is to be routed through the VPN
Do not alter clients' DNS server settings
Have clients use the same DNS servers as the Access Server host
Have clients use specific DNS servers