How to implement DRAD Server with AD integrated DNS zone RRS feed

  • Question

  • We are implementing DR in our org and we are facing a challenge with the DNS entries because our SAP team used Storage replication and kept same Hostnames in DR as in Production, so when we try to do testing in DR, this new i.p is getting updated in DNS and getting replicated to all the Domain Controllers and causing Production issues.

    We tried this, created a new DC with DNS in DR and put the replication schedule for 7 days, so for the given period ,it worked fine and no entry from the DRDC got replicated to production DC's.

    So once our testing was done, i manually removed the entries from DRDC and then even uninstalled only DNS on that DC and re-installed.

    I didnt find any new entries when i checked at that time, but today we found that a lot of new entries were created and some were deleted from the production DC's after that replication happened.

    So,can anyone please suggest, how to proceed in this type of scenario. We dont have any support of Microsoft , so I am trying to search for help here.

    We have Exchange but i am using DAG so no challenges for it, only problem is with the SAP boxes where they are using same Hostnames in Prod and DR.


    • Edited by mdimthyas Sunday, June 10, 2018 5:20 AM
    Sunday, June 10, 2018 5:20 AM


  • Hi,

    there are three general approaches to DR and you are usually very liable to get into Trouble mixing them:

    1. Using backup for DR, so in case of disaster you restore to DR site rather than to prod site.
    2. Site resilience = using the built-in availability mechanisms for populating the DR site --> that is what you are using for AD and Exchange and what you'd probably be using for SQL as well.
    3. Site replication = using non-application-aware methods for populating the DR site --> that is what your SAP Team has done.

    Short answer: you're stuck there.

    Long answer is this: You need to move your DR strategy to one of the approaches listed above. Since replication (as in 'storage replication') doesn't work all that well with AD or Exchange, #3 is probably out of the question. So your options are:

    1. Check with your backup team if going for #1 is possible with the backup technology your organisation is using. This way you can create a separate DR environment and even have the DR environment reflect CONSISTENTLY the state of the prod environment as of several days ago. This is useful if the disaster in question is of the data-manipulating variety.
    2. Check with your SAP Team if they can go from block replication to application-aware replication.

    Evgenij Smirnov

    I work @ msg services ag, Berlin ->
    I blog (in German) @
    my stuff in PSGallery -->
    Exchange User Group, Berlin ->
    Windows Server User Group, Berlin ->
    Mark Minasi Technical Forum, reloaded ->

    In theory, there is no difference between theory and practice. In practice, there is.

    • Marked as answer by mdimthyas Sunday, November 25, 2018 5:49 AM
    Sunday, June 10, 2018 11:02 AM