Psequel connect to hostname dynamically assigned
You have no more control over it or ask your ISP to configure the DNS forwarder. Since you are using a laptop, the DNS servers used by your computer are most likely specified by your ISP. So you indeed need a custom DNS server in using FQDN of the server in connection strings for your clients to connect from on-premise VM to the Azure SQL server. If the answer to the first question is "No", is there another way to connect an on-premises computer with dynamic IP to an Azure SQL server using any other Azure application(s)?įirst of all, you can not use FQDN without DNS service. Is there any possibility to establish connection between an on-premises computer with dynamic IP and an Azure SQL server using a private endpoint but without own DNS server? Unfortunately, the laptop does not have access to any custom DNS, so this solution does not suit. It recommends using your own DNS server to resolve the SQL server FQDN to the local IP. I found the following article: The article is great. But without hosts file, the laptop always tries to connect to the SQL server via its public endpoint/address. After this, I can successfully connect to the SQL server IP using telnet, and if I resolve the SQL server FQDS in hosts file, I can connect to the server via SSMS.
Also, I added a private endpoint to the SQL server. To do this, I created a virtual network gateway and connected the laptop to the gateway. I am trying to connect an on-premises laptop with dynamic external IP to our Azure SQL Server.