{"id":11271,"date":"2026-05-18T14:46:29","date_gmt":"2026-05-18T19:46:29","guid":{"rendered":"https:\/\/stevepedwards.today\/DebianAdmin\/?p=11271"},"modified":"2026-05-18T14:46:29","modified_gmt":"2026-05-18T19:46:29","slug":"azure-dns-alias-with-suffix-xxx-cloudapp-azure-com","status":"publish","type":"post","link":"https:\/\/stevepedwards.today\/DebianAdmin\/azure-dns-alias-with-suffix-xxx-cloudapp-azure-com\/","title":{"rendered":"Azure DNS Alias with suffix xxx.cloudapp.azure.com"},"content":{"rendered":"
<\/div>\n

<\/path><\/svg><\/i> \"Loading\"<\/p>\n

<\/div>\n

Azure DNS Alias with suffix xxx.cloudapp.azure.com<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

<\/p>\n

Configure the VM pip for DNS:<\/p>\n

<\/p>\n

Log in to the VM via RDP and setup IIS as prior exercises:<\/p>\n

<\/p>\n

Check the default server IIS webpage exists locally via RDP in Edge browser:<\/p>\n

<\/p>\n

Configure a public IP address (Configure a DNS idle time, name, and alias record for your public IP address.):<\/p>\n

<\/p>\n

Configure:<\/p>\n

<\/p>\n

Give a DNS name for the VM, that has the applied suffix;<\/p>\n

winvmfordns<\/p>\n

.northeurope.cloudapp.azure.com<\/p>\n

<\/p>\n

Check the PIP is available from WSL2 :<\/p>\n

steve@baby:~$ nmap 20.107.172.166 -Pn<\/p>\n

Starting Nmap 7.94SVN ( https:\/\/nmap.org ) at 2026-05-18 19:38 BST<\/p>\n

Nmap scan report for 20.107.172.166<\/p>\n

Host is up (0.066s latency).<\/p>\n

Not shown: 999 filtered tcp ports (no-response)<\/p>\n

PORT STATE SERVICE<\/p>\n

3389\/tcp open ms-wbt-server<\/p>\n

We need to open port 80 to the win server on the public IP with an Inbound Rule in WinVM-for-DNS<\/strong>\u00a0| Network settings :<\/p>\n

<\/strong><\/p>\n

The port is open from WSL2:<\/p>\n

steve@baby:~$ nmap 20.107.172.166 -Pn<\/p>\n

Starting Nmap 7.94SVN ( https:\/\/nmap.org ) at 2026-05-18 19:48 BST<\/p>\n

Nmap scan report for 20.107.172.166<\/p>\n

Host is up (0.059s latency).<\/p>\n

Not shown: 998 filtered tcp ports (no-response)<\/p>\n

PORT STATE SERVICE<\/p>\n

80\/tcp open http<\/p>\n

3389\/tcp open ms-wbt-server<\/p>\n

Check the IIS site is available by IP in Chrome:<\/p>\n

<\/p>\n

Now to check the above setup Azure DNS A record http:\/\/winvmfordns.northeurope.cloudapp.azure.com\/<\/a> works:<\/p>\n

<\/p>\n

If you have an external, owned domain name, you can use your provider website DNS record settings to route your private domain name to the Azure VM by linking the Azure PIP to your private domain name, then once the DNS has propagated, the DNS for that site will point to the Azure VM, e.g.:<\/p>\n

<\/p>\n

<\/p>\n

steve@baby:~$ nmap -Pn azure.stevepedwards.today<\/p>\n

Starting Nmap 7.94SVN ( https:\/\/nmap.org ) at 2026-05-18 20:30 BST<\/p>\n

Nmap scan report for azure.stevepedwards.today (20.107.172.166)<\/p>\n

Host is up (0.11s latency).<\/p>\n

Not shown: 998 filtered tcp ports (no-response)<\/p>\n

PORT STATE SERVICE<\/p>\n

80\/tcp open http<\/p>\n

3389\/tcp open ms-wbt-server<\/p>\n

Now I have a legit azure alias to test future DNS exercises via my main ISP site:<\/p>\n

<\/p>\n

If you ever need to change a record and want to ensure you aren't fighting any<\/em> local machine caching whatsoever while testing your Azure VMs, you can flush your local computer's DNS cache instantly via the terminal:<\/p>\n