Hi,
This is stated:
"Use the Fully Qualified Domain Name(FQDN) of the server in connection strings for your clients. Any login attempts made directly to the IP address shall fail by design."
I do not understand this. You have a private endpoint and thereby an IP from your Azure subnet. For example 10.10.10.10. If your on-premise server routes this IP through the ExpressRoute why would you need to use the FQDN?
Regards Peter
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@theheatDK Thank you for reaching out.
We are actively investigating and will get back to you soon.
The private IP routes traffic to SQL Gateway in the region ( behind the scenes) via the Azure backbone. Hence you need to provide FQDN so we can route traffic to the logical server
Thanks @rohitnayakmsft
Then it makes sense :-)
I will try to update the documentation note with this explanation.
Regards Peter
FQDN is same as the main endpoint. How does it differ since we cannot differ FQDN.
Not sure I understand. If you access is from inside Azure you can create a Private DNS zone. If it is from on-premise you can add an entry to the local hosts file or create an entry in you dns server.
Hi,
Thanks for prompt response ! we are accessing from on prem network through express route. We will make the entry and try that.
Regards,
Vishal
Hi,
We are able to connect when we enter the FQDN and the IP in host file.
However, struggling to provide instruction for A record since we have our company domain .companyname.com and we can make entry but it comes with our subdomain when we request.
Also, refered to : https://community.spiceworks.com/topic/2200620-dns-zone-without-fqdn
Regards,
Vishal