High Availability DNS solution for AD

Tiras25
Tiras25 used Ask the Experts™
on
Considering HA for company's DNS infrastructure.  We have hybrid on-prem and cloud Azure setup.  Thinking off having a primary DNS on-prem Domain Controller and secondary on Azure as a failover.  Anyone has a similar setup and can suggest something.
 Please do.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
DNS was designed from the beginning with high availability in mind. Just set the two up to do zone transfers for replication, use DHCP to configure clients to use the internal DNS as a primary, with the Azure hosted one as a secondary.

If you want you can configure domain registration to point to both DNS server as well.

This stuff has not changed much in the last few decades.
kevinhsiehNetwork Engineer

Commented:
Just put DNS where your domain controllers are.
Architect
Distinguished Expert 2018
Commented:
Put dc in Azure if you have any server infrastructure or applications deployed in Azure which need ad authentication
OR
Consider it as DR dc and you can use it to rebuild ad services when disaster happens
If you put it as secondary on devices, when disaster happens you will loss connectivity to azure dc as well as internet and vpn both are required to connect to that dc and disaster means you loss everything incliding onpremise setup, internet and so on.

You already must be having multiple dc/dns servers on premise which is already highly available, the condition never comes under normal circumstances that *all* onpremise dcs are down / failed and you need to contact cloud dc, further if ad gets currupted, you need to undergo forest recovery where you need to rely on last good AD system state backup before corruption and in that case your azure dc can't help you as it also needs to be decommissioned and redeployed
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

nociSoftware Engineer
Distinguished Expert 2018
Commented:
DNS is setup for HA, create a master zone somewhere and some slaves on other DNS servers.
Then any update will be propagated BY DNS servers if a zone gets updated on the master.
DHCP servers should point to the master DNS server for updating.

If a Master is irretrievably lost then a slave can be promoted to master to continue the work.
This is a part of DNS that exists since it's inception.
Shaun VermaakTechnical Specialist
Awarded 2017
Distinguished Expert 2018
Commented:
Thinking off having a primary DNS on-prem Domain Controller and secondary on Azure as a failover.
This is a very common design, although usually two on-prem. Setup DNS as Active Directory Integrated
DrDave242Principal Support Engineer

Commented:
I second the advice to use AD-integrated DNS zones. Then you don't have to worry about all of the primary/secondary zone transfer setup, as DNS replication will be handled by AD.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial