Naked domain support using GoDaddy and Azure Websites

Getting a naked domain working properly seems to be one of those secrets of the internet that people in the know protect under threat of violence.

Different DNS providers and hosts handle this differently, but here’s how I got it working with Azure Websites and GoDaddy.

In my case, I wanted to get both http://www.rescuepal.com and http://rescuepal.com to point to my website. Preferably, I also wanted http://rescuepal.com to work without a redirect – I wanted the user to actually see http://rescuepal.com in the address bar.

The Azure management portal pretty much tells you all you need to know when configuring a custom domain for your site. After you enter the domain, it does some validation to make sure the necessary DNS entries are in place – and let’s you know if they’re not.

NakedDomain-Azure

 

Pretend for a second that I entered www.rescuepal.com (not www.mycustomdomain.com as in the screenshot). The error message tells me that I need a CNAME record awverify.www that points to awverify.rescuepal.azurewebsites.net.

After configuring that in GoDaddy, http://www.rescuepal.com works as a custom domain for http://rescuepal.azurewebsites.net.

To get the naked domain http://rescuepal.com to work as a custom domain, create a CNAME record awverify that points to awverify.rescuepal.azurewebsites.net

Here you can see the two CNAME records in GoDaddy:

NakedDomain-GoDaddyDNS

and the custom domains configured in the Azure Management Portal:

NakedDomain-AzureWebsitesCustomDomains

 

Hope this helps

4 comments

  1. Nitin M says:

    Thanks George… it really helped me get the website up and running..

  2. Kousha Nejad says:

    Hi George, I’ve struggling for a few days, googling, calling GoDaddy and Azure, and your simple instruction worked perfectly, and BIG thank you

  3. Ignacio Fuentes says:

    Hey George. Nice info. This is where I am currently at but I actually wanted the user to be redirect to the naked domain if they manually entered www. Like twitter does it. Is that something that needs to be done in the app or the DNS can solve it?

  4. georgedurzi says:

    Ignacio, twitter does a 301 redirect on http://www.twitter.com to twitter.com. You can see it happening in your browser’s developer tools; e.g.: in Chrome, click the Network tab.

Leave a Reply to Nitin M Cancel reply

Your email address will not be published. Required fields are marked *