Part 1: Create and deploy a website with Microsoft Azure web app service plan
Part 2: Configure a custom domain in Azure Static Web Apps
After first part of installing web apps on Microsoft Azure, I purchased (I already have it) custom domain name from domain hosting provider. My deployed website on Azure web apps is working fine softcurry.azurewebsites.net, As it can be seen in the screenshot custom domain name softcurry.com is not working. To get it working I will need to map custom domain name dns with web apps information.
To get custom domain worked on web apps, go to the Custom Domains menu on left hand side pane. Click on the + Add custom domain. Type Custom domain and click Validate button. Validation will verify domain hostname availability and domain name ownership (Whether softcurry.com domain belongs to me). To verify ownership I will need to add/map A resource records and TXT records on domain name provider web site (There is another option of CName record), in the bottom Azure is providing what information need to be register at domain name provider portal as below example, There is A record and TXT record need to be created. Follow the table generated by Azure.
Example of Azure Custom domain validation table. ================================== | Type | Host | Value | ================================== | TXT | asuid | BEDse374jf834j | ---------------------------------- | A | @ | 126.96.36.199 | ----------------------------------
The portal for Domain name provider may different but the the process I am following is here might be common with other Domain Name provider. I logged in on to my Domain Name Provider website, Selected domain name which I have purchased. On the next page find DNS management section and click Manage Domain to map your Domain to a web hosting or email service, set Domain aliases, etc. Next go to A record tab button and click Add A Record.
For A record fill the information with HostName as @, associated Destination IPv4 Address as mentioned above from azure custom domain validation table, Click Record and verify Host A record is added successfully. Next click on TXT Records tab button then Add TXT record.
On the TXT record again check the table mentioned on the Azure custom domain validation table. Fill up Hostname asuid and associated value. Check the newly added TXT record in the list.
Next on the Web Apps go to Custom Domains then Add custom domain, click Validate and this time Azure will verify Domain ownership by changing the icon to green. In the last click Add custom domain. I have successfully added Assigned custom domain, it is without https so ssl state is obvious will be not secure.
Just beware that depending on your DNS provider it take up to 48 hours for the DNS entry changes to propagate globally. You can verify that the DNS propagation is working as excepted by using http://digwebinterface.com/. In my case it was very fast, I just flushed dns resolver cache using ipconfig /flushdns on cmd prompt, If it is still not working wait for some time.
By reopening custom domain on browser it shows checks for the latest mapping and shows the website, At the moment my custom domain is using http port, to change it to https, I will add certificate in next article.
PART 1 : MICROSOFT AZURE CREATION AND CONFIGURATION OF VPN TUNNEL SERIES
PART 2 : MICROSOFT AZURE CREATING RESOURCE GROUP
PART 3 : MICROSOFT AZURE CREATING AND ADMINISTERING VIRTUAL NETWORK (VNET)
PART 3.1 : MICROSOFT AZURE POWERSHELL CREATING AND ADMINISTERING VIRTUAL NETWORK (VNET)
PART 4 : MICROSOFT AZURE CREATING AND ADMINISTRATING LOCAL NETWORK GATEWAY VPN
PART 4.1 : MICROSOFT AZURE POWERSHELL CREATING AND ADMINISTRATING LOCAL NETWORK GATEWAY
This post first appeared on Tales From Real IT System Administrators World And Non-production Environment, please read the originial post: here