Hello Group,
As part of a POC, I am in the process of creating a domain-independent (or) AD detached cluster and then create a SQL availability group on Azure VMs (using windows 2016 & SQL 2016)...Performed the following activities...
1) Created a windows fail-over cluster with 2 VMs located in different regions. Created a VM for DNS server in one of the regions and both the VMs were configured to point to the same DNS (using VNET-VNET integration).
2) Created a SQL availability group & listener from SSMS on the primary SQL VM.
3) Created internal load balancer (ILB) for each of the VMs and configured these ILB IP as part of listener dependency.
4) When i do a fail-over from SQL primary SSMS, i see that the respective Primary ILB endpoint is going Offline as expected, and the secondary's ILB endpoint is coming Online (as expected) in the listener section from "Failover cluster Manager". I am also able to connect to the end point using IP address & we are good so far...
My understanding is - when i do a fail over, i should be able to connect to the SQL server using listener name itself (and listener will internally take me to the ILB endpoint that is "Online").
My problem now is - i am not able to get the listener name (which is a DNS name) return the IP address of the ILB IP address that is "Online". In other words i am not sure how/where to establish a mapping between listener name/DNS name to the ILB IP address that changes dynamically (when a fail-over is performed).
As of now, when i do a "ping <<listener>" from the primary SQL VM, i get a response "Ping request could not find host <<listener>>. Please check the name and try again."
Please advise on how to resolve this issue & any inputs on this would be of great help...
Thanks & Regards
Kiran...