Hello Friends,

Today, let’s discuss about one issue, which I addressed, during the configuration of custom domain on our Azure DNS in my last article. It is a common issue we will face, if we don’t follow the configuration steps properly.

Tool Installation Articles :

1. Configure Azure Command Line Interface ( Azure CLI) On Windows
2. Configure PowerShell For Microsoft Azure Az Module On Windows

Previous Azure Series :

1. Learn Basics Of Azure Networking In 100 Hours
2. Learn Basics Of Microsoft Azure Storage services
3. Learn Basic Of Azure Active Directory And Azure Identity And Access Management
4. Azure DevOps – Learn at one place
5. Learn Basics Of Lift-And-Shift Migration To Azure

If you have missed our previous articles on networking, please check them in following links.

Part 4 – Network Security Group (NSG) in Azure

Part 5 – Basics of Azure Application Gateway

Part 6 – Azure Application Gateway Features

Part 7 – Create An Application Gateway With URL-Based Routing Configuration- 1

Part 8 – PowerShell To Create An Application Gateway With URL-Based Routing Configuration- 2

Part 9 – Configure Custom Domain In Azure DNS

Next Article : Part 11 – ExpressRoute

In our last exercises, we had to configure our custom domain (manasmoharana.xyz) in Azure. As per the procedure, we should first configure all records ( One “CNAME” record, one “A” record and one “TXT” record) in custom domain provider site (Godaddy.com) and then configure/add “CNAME” record for custom domain in Azure. So that it could validate the domain availability and ownership from domain provider .

In our exercises, we had only added One CNAME DNS record, before going to configure custom domain in Azure as shown in following figure.

So when we were trying to add a CNAME record for our custom domain in Azure, it failed with validation as shown in following figure.

To fix the above issue, we went back to domain provider’s DNS and added the missing two new records (One “A” record and one “TXT” record ) as shown here.

After configure all records in domain provider DNS, we try to re-validate the custom domain in Azure. And this time it successfully validate and allow to add the “CNAME” record for our custom domain, as shown in the following figure.

Learning :

Here , if I understood correctly, we need to first configure all required records for all format in domain provider DNS, before we configure the equivalent record in Azure DNS. So that when azure try to validate the new record, it will find the similar one in domain provider’s DNS and validate it.

For example if we want to add a new sub-domain and want to access the site with new sub domain ( home.manasmoharana.xyz), then before configuring the record in Azure DNS , we need to add a following wildcard (*) CNAME record in domain provider’s DNS as shown in following figure.

We can configure the CNAME record in azure for “home.manasmoharana.xyz” once we have done with the above configuration as showing here.

I hope it will help you to fix this issue. My next article of this series is Part 11 – ExpressRoute .

Thanks for reading  🙂

Keep reading, share your thoughts, experiences. Feel free to contact us to discuss more.

If you have any suggestion / feedback / doubt, you are most welcome. Stay tuned on Knowledge-Junction, will come up with more such articles