none
Change of DNS server setting caused Exchange outages! RRS feed

  • Question

  • I am trying to google/bing my way through this, but here are the main points:

    • All remote Exchange servers had a) static IP addresses and b) were instructed to use DNS servers in Edmonton and Calgary
    • If WAN links dropped, they lost DNS
    • SOLUTION! Point remote servers to the domain controller in that location as the primary DNS server. WAN outage means Exchange still resolves names locally.

    Well the day came and we add the local DNS server for each remote site as the primary DNS server at the top of "DNS server addresses, in order of use" portion of advanced TCP/IP settings dialogue box.

    • A reboot is performed
    • Voila! Exchange shits the bed! Hub transport servers in Edmonton and Calgary cannot resolve remote server names; as in no host(a) record exists for them anymore. And we have a 91 minute outage until the DNS is sorted out (ipconfig /registerdns run on each server).

    Has anyone encountered this or have some deep knowledge of DNS (relative to my own) that could at least throw out a theory as to why this might happen?


    • Edited by Kellar24 Tuesday, April 28, 2015 8:11 PM
    Tuesday, April 28, 2015 8:10 PM

Answers

All replies

  • Hi, please issue Get-ExchangeServer -Identity "ServerName" -status | fl and check:

    CurrentDomainControllers
    CurrentGlobalCatalogs  
    CurrentConfigDomainController

    The server must been linked to the wrong server. You can change that in powershell too.


    Regards, Philippe

    Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )

    Answer an interesting question ? Create a wiki article about it!

    Wednesday, April 29, 2015 1:23 AM
    Moderator
  • We think it has to do with a glitch in the DNS client on server 2008 R2:

    https://support.microsoft.com/en-us/kb/2520155/en-us#appliesto

    Wednesday, April 29, 2015 6:29 PM
  • Hi,

    The DNS server assignment changing of Exchange server causes related DNS resource record losing on the previous DNS server.

    Try to install the hotfix on your server, if it is not applied to your server’s edition, considering to use the workaround way to manually registry DNS record.

    Best Regards,
    Eve Wang


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Thursday, April 30, 2015 1:39 AM
    Moderator