Post reply

SQL Multisubnet DNS issue

  • September 1, 2022 at 6:59 am

    Go to Answer

    #4082737

    Hello

    We have a situation where we need to setup AlwaysOn configuration in hybrid mode (2 servers on on-premises and 2 on Azure hosted hosted under same cluster) with listener having 2 different IP's from 2 different subnets (one IP of Azure subnet and other of on-premises subnet)

    Since we had application connection issues we had to remove the Azure subnet IP. Yet somehow there is Azure IP getting configured automatically every 24 hours. I'm not sure how and from where this IP is getting registered back.

    Any idea where to start and how to stop this auto registering of Listener IP that is not active for now.

    Thanks in Advance

    Regards,

    Preethi

  • September 2, 2022 at 7:10 am

    #4083145

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • September 2, 2022 at 9:41 am

    Answer

    #4083190

    Have you set the parameter “RegisterAllProvidersIP” to 0?

     

    This will tell the cluster to only register the primary IP for the listener.

    Either that or you must go and change your connection strings to include the “MultiSubnetFailover=True” attribute.

  • September 9, 2022 at 6:06 am

    #4085658

    Hi,

    I set this parameter RegisterAllProvidersIP” to 0, its working fine now.

    Thank you and sorry for late response since I had to wait to performing testings.

     

     

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply