Launch: Migrating an active Site to Azure App Service

James Vidler -

Are you migrating an existing site to Azure App Service and can't afford any downtime? If so, you'll need to take some pre-preemptive action to allow Azure App Service to recognize your custom domain(s) BEFORE your customer switches over their DNS.

By default, if you try to add your custom domain names to Azure App Service and they don't already point via an A or CNAME record to the Azure App Service then Azure will tell you it can't validate those hostnames. 

Luckily, Azure has a way to bind the domain name preemptively using TXT records and is nicely explained in their knowledge base article Migrate an active DNS name to Azure App Service.

Want the short and sweet version?

Create a TXT domain verification record

To verify domain ownership, Add a TXT record. The TXT record maps from awverify.<subdomain> to  <subdomain>.azurewebsites.net.

The TXT record you need depends on the DNS record you want to migrate. For examples, see the following table (@ typically represents the root domain):+

 

DNS record example

TXT Host

TXT Value

@ (root)

awverify

<sudomain>.azurewebsites.net

www (sub)

awverify.www

<subdomain>.azurewebsites.net

* (wildcard)

awverify.*

<subdomain>.azurewebsites.net

 

This needs to be done for each root domain.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.