none
Windows 2008R2 DNS not shifting to alternative DNS if Primary failed

    Question

  • WE are having For DCs  having AD integrated Zones installed.

    At our default AD Site we having Two DCs or Which are DNS too.

    At client End We manullay set the TCP/IP settings for DNS.

    eg : Primary DNS: 130.0.0.2

    Alternative DNS: 130.0.0.5

    Problem Started when due to some reason we shutdown makes or offline the Primary DNS . Client dint automatically switch to alternative DNS for Resolution. 

    I have verified by this NSlookup CMD.

    Wednesday, October 02, 2013 5:19 AM

Answers

  • That's not the operating system behavior (which should fail over to the secondary if the primary is not available) - so this potentially this might be something application specific . Have you verified that the name resolution works as intended when using native OS tools - e.g. when connecting to a network share or pinging a server by name?

    If that's NOT the case, then verify that the client computer in question can actually resolve names by using the secondary DNS - which can be done by running nslookup in the manner described by Denny

    hth
    Marcin

    Wednesday, October 02, 2013 11:55 AM

All replies

  • Hi,

    nslookup has no fallback to secondary dns, it only looks for the default/primary dns server.

    "Looks up information for ComputerToFind using the current default DNS name server"

    You can only try this:

    nslookup <computername> <ip of dns server>

    http://technet.microsoft.com/en-us/library/bb490950.aspx

    Wednesday, October 02, 2013 6:05 AM
  • But thats not concerning point actually my local application ruining in our environment and when user tries to resolve or hit the application server, it does not go for alternative DNS if Primary is unavailable. 
    Wednesday, October 02, 2013 6:34 AM
  • Check the DNS server IP into your application. Configured DNS server into that application should up & running.

    Best regards Biswajit Biswas Disclaimer: This posting is provided &quot;AS IS&quot; with no warranties or guarantees , and confers no rights. MCP 2003,MCSA 2003, MCSA:M 2003, CCNA, MCTS, Enterprise Admin


    Wednesday, October 02, 2013 6:43 AM
  • That's not the operating system behavior (which should fail over to the secondary if the primary is not available) - so this potentially this might be something application specific . Have you verified that the name resolution works as intended when using native OS tools - e.g. when connecting to a network share or pinging a server by name?

    If that's NOT the case, then verify that the client computer in question can actually resolve names by using the secondary DNS - which can be done by running nslookup in the manner described by Denny

    hth
    Marcin

    Wednesday, October 02, 2013 11:55 AM