Failover Cluster DNS changes/updates

Jason P 146 Reputation points
2024-10-16T10:04:58.8+00:00

Hi All,

We have a failover cluster in place for our SQL environment. I have noticed that when it fails over it creates a new DNS record for the new IP of the SQL listener.

I have removed all the DNS records, created one and then I have set up the DNS record to have the CNO and Nodes have full control of that DNS record.

When I do a failover I see that a new DNS record is created for the new IP, but the old one is still there. It does not seem to just change the DNS record. So now we have an issue of DNS round Robin in play.

Is there a way to fix this issue?

Thanks

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,980 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
1,008 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Jason P 146 Reputation points
    2024-11-01T18:30:51.5933333+00:00

    I found the solution.

    I had to look through the registry under HKEY_LOCAL_MACHINE\Cluster\Resources

    Find the listener cluster resource GUID. Expand and look in Parameters

    Change RegisterAllProvidersIP to 0

    Did this on both nodes. Failed over to other node and now it updates only one DNS entry (as long as it has the CNO in there with Full Control)

    1 person found this answer helpful.
    0 comments No comments

  2. LucyChenMSFT-4874 5,060 Reputation points
    2024-10-17T02:28:09.6866667+00:00

    Hi @Jason P,

    Thank you for your reaching out and welcome to Microsoft Q&A!

    It sounds like there are still a few records in there. You can check for SRV records using NS lookup:

    How to verify that SRV DNS records have been created for a domain controller

    Also under the zone properties, make sure it is removed from the Name Servers tab.

    I hope this helps! If you have any more issues or need further assistance, feel free to share with us!

    Best regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notifications


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.