Backup Domain Controller at Cloud failed to function

Ikhsan Ali 1 Reputation point

Hi All.

I have a 2 VM in my local network, which serves as PDC and BDC. Also, I have installed and setup a BDC (using same OS which is Windows Server 2016) at VM in the Cloud (AWS), which serves at Disaster Recovery. I use IPSEC VPN from my local network to AWS. Both servers functioned properly and I can see the replication in all servers.

Now, I would like to test the DR scenario. I turned OFF all Servers in my local network. I am assuming the BDC in the cloud will be functioned properly. but it's not. I can open DNS Manager and it showed my domain. but when I tried to open Active Directory Sites and Services and Active Directory Users and Computers, it failed with message :

"Naming Information cannot be located because:
The specified domain either does not exist or could not be contacted".

Just additional notes:

  1. The BDC in the cloud can access internet and can access my local network (with the condition of both DC is turned off).
  2. When I ping my domain, it goes to the BDC in my local.
  3. When I nslookup to my domain (from my BDC in the cloud), it showed all three DCs, and default address : localhost
  4. If I turn ON the BDC in my local network, then the BDC in the cloud will be functioned properly. Also, the BDC in my local network is functioning properly. but this is not the scenario that I want.

Any idea how to solve this?

Thank you in advance.

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,429 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,210 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Anonymous

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\dc3.txt

    then put unzipped text files up on OneDrive and share a link.

  2. Barzin Hosseini 91 Reputation points


    When your local DCs go down the site coverage must run and your cloud DC must take the responsibility of local. I prefer to say it is DNS issues. please check these possible issues in DNS server :

    The NS server IP and FQDN in your DNS server.
    Check the CNAME and it's GUID for each server.
    Try to create conditional forwarder in local DC with forest scope for cloud ( after that force to replicate).

    Additional causes :

    The date and time for both local and cloud server

    Firewall rules
    more information about ports :