Post reply

3 node Always On but only 1 node points to correct listener IP

  • September 13, 2021 at 7:19 pm

    #3929212

    if you do an nslookup to the listener do you get all the IPs back?

    if so you need to either disable registeraipproviders

    or the recommended approach, change your applications to use the multisubnetfailover=true connection string attribute.

  • September 13, 2021 at 7:28 pm

    #3929213

    Hey Ant-Green,

    thank you for your reply,

    so very very weird... on Server 2 and 3, when i do the NSlookup, the ip addresses in order are never consistant.. example

    first time i do nslookup on server 2 or 3:

    it would say address:

    192.168.2.26

    192.168.3.26

    192.168.1.26

    then the second time it would change the order:

    192.168.3.26

    192.168.2.26

    192.168.1.26

    what i need it to do is point to 192.168.1.26 then the others second, as right now 192.168.1.26 is the pingable working, also, I am trying to point my SSRS server to the Always On listener, so not sure if it has that option: multisubnetfailover=true or maybe it does?

  • September 13, 2021 at 7:39 pm

    #3929219

    Yeah you will get results in varying order depending which dns server responds to the query.

    SSRS does support multisubnetfailover=true in the connection string.

    that is the official stance from Microsoft, if you have multiple IPs use the right connection string attributes.

    if the driver doesn’t support the options then you need to switch off the option and then your at the mercy of dns replication and having downtime each time the replica fail over.  And we all know all problems point to DNs right so best to not mess with that and use MSF=True option.

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

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