You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@@ -270,7 +270,7 @@ Update the Spoke VNet custom DNS settings to point at your *az-dns-vm* VM inside
**Reboot** your *az-mgmt-vm* VM so that it picks up the new DNS settings.
Or **ipconfig /renew ** should work. Check with ipconfig /all
( Or **ipconfig /renew ** should work. Check with ipconfig /all )
From your *az-mgmt-vm* VM re-run your nslookup command to check the IP address returned for your SQL Server. Notice how the DNS server used is now 10.0.0.4 (the IP address of your *az-dns-vm* VM), but the A record returned has now regressed to using the public VIP of SQL. Access to your SQL Server will not work in this configuration as you are not utilising your Private Endpoint.
