![the dns server is waiting for active directory domain services 4013 the dns server is waiting for active directory domain services 4013](https://cdn.slidesharecdn.com/ss_thumbnails/edb3a866-0732-4013-91f9-acc65adea70e-150430083632-conversion-gate02-thumbnail-4.jpg)
Ensure that it meets the following requirements: The domain controller that is replicated by using Site Recovery is used for test failover. You can use Site Recovery to protect the virtual machine that hosts the domain controller or DNS. For failover, you can use the additional domain controller on the target site.
![the dns server is waiting for active directory domain services 4013 the dns server is waiting for active directory domain services 4013](https://4.bp.blogspot.com/-T-4IES4RcAU/UGHYNOTlk4I/AAAAAAAAB9c/RfiWN0_eAPM/s1600/pic4.png)
For test failover, you can use a domain controller that's replicated by Site Recovery.
![the dns server is waiting for active directory domain services 4013 the dns server is waiting for active directory domain services 4013](https://www.mcmcse.com/microsoft/guides/70-411/images/dns_zones8.jpg)
In this case, we recommend using Site Recovery to replicate the domain controller to the target site, either in Azure or in a secondary on-premises datacenter. If you have only a few applications and one domain controller, you might want to fail over the entire site together.The additional domain controller can be in Azure, or in a secondary on-premises datacenter. If you have multiple domain controllers in your environment, you also must set up an additional domain controller on the target site.You must set up Site Recovery replication, on at least one virtual machine (VM) that hosts a domain controller or DNS.Review the support requirements for all components.If you're replicating to Azure, prepare Azure resources, including a subscription, an Azure Virtual Network, a storage account, and a Recovery Services vault.You should be familiar with Active Directory and Site Recovery before you begin. It includes prerequisites, and failover instructions.
#THE DNS SERVER IS WAITING FOR ACTIVE DIRECTORY DOMAIN SERVICES 4013 HOW TO#
This article explains how to create a disaster recovery solution for Active Directory. Then, fail over the other applications, using application-specific recovery plans. You can first fail over Active Directory using Site Recovery. If you have deployed Active Directory for multiple applications in your primary site, for example, for SharePoint and SAP, you might want to fail over the complete site. You can have Active Directory up and running in a few minutes. When a disruption occurs, you can initiate a failover. You can use Site Recovery to create a disaster recovery plan for Active Directory. When you set up disaster recovery for applications, you often need to recover Active Directory and Domain Name System (DNS) before you recover other application components, to ensure correct application functionality. Enterprise applications such as SharePoint, Dynamics AX, and SAP depend on Active Directory and a DNS infrastructure to function correctly.