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.
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.
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:
and the custom domains configured in the Azure Management Portal:
Hope this helps