Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Availability Group Listener DNS Response


Availability Group Listener DNS Response

Author
Message
johnmcp
johnmcp
Valued Member
Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)

Group: General Forum Members
Points: 58 Visits: 341
I'm trying to understand something about Availability Group listeners that are configured on multiple subnets...
I have an availability group listener with two IP addresses on different subnets. Obviously, only 1 IP is online. If I do an nslookup against the listener name it comes back with both IP addresses as expected. If i ping the listener name, I will get a reply provided it resolves to the IP address that is currently online. If however, it resolves to the other IP address that is not online, it will not reply.
So, this leads me to understand that if I am connecting to an Availability Group via the listener name, and my client is not Multi-Subnet aware, there's a good chance that I will not be able to connect because the request may resolve to the wrong IP address. Is this correct?
Kwisatz78
Kwisatz78
SSChasing Mays
SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)SSChasing Mays (607 reputation)

Group: General Forum Members
Points: 607 Visits: 1821
I just did a quick read of this:

http://msdn.microsoft.com/en-gb/library/hh213080.aspx#CreateAddiitListener

However if using 2 static IPs of different subnets and you use the listener name in your connection string, then the client you use should resolve the listener name to the correct IP for that subnet and hence you should be connected to your current primary.

Thats how I read it although I could be wrong.
johnmcp
johnmcp
Valued Member
Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)Valued Member (58 reputation)

Group: General Forum Members
Points: 58 Visits: 341
Kwisatz78 (2/18/2013)
I just did a quick read of this:

http://msdn.microsoft.com/en-gb/library/hh213080.aspx#CreateAddiitListener

However if using 2 static IPs of different subnets and you use the listener name in your connection string, then the client you use should resolve the listener name to the correct IP for that subnet and hence you should be connected to your current primary.

Thats how I read it although I could be wrong.


Yes but this depends on the client right? If the client does not support multi-subnet failover then I don't think its safe to use the listener name because it does not know that the server could be listening on more than one address. This is what I have found from testing but I just wanted to confirm that this is the expected behavior.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search