A couple of days ago I set up a new site in Azure and modified my DNS records to point to the site. I am unable to add the custom domains through the management tool or the portal.
The error I see is
"A CNAME record pointing from mysite.com to mysite.azurewebsites.net was not found. Alternative record awverify.mysite.com to awverify.mysite.azurewebsites.net was not found either."
(Changed my real domain to mysite as I'd rather not put that here).
The worst part is when I visit "mysite.com" it is showing me an Azure 404 page saying "The web site owner has registered a custom domain to point to the Microsoft Azure Web Site, but has not yet configured Azure to recognize it.".. I'm trying to configure it but Azure is not letting me!!!
For my DNS i have:
an A-Record pointing to my virtual IP
a second A-Record for www pointing to the IP (I did have www as a CNAME-Record for mysite.azurewebsites.net but that didn't seem to be working)
a CNAME-Record for awverify.mysite.com to awverify.mysite.azurewebsites.net
a CNAME-Record for awverify.www.mysite.com to awverify.www.mysite.azurewebsites.net
I thought maybe it was taking forever to propagate but it's been 2 days now.
Thanks!
Although it usually takes a couple of minutes for DNS records to be available, it can take up to 72 hours for DNS records to propagate. If it is all configured correctly (and looking at the list you posted, it is), it's a matter of waiting for it to propagate.
Related
There are certain variations to this question but none answered mine.
I have a custom domain aaaskills.mydomain.com pointing to azure website.
This was done by setting CNAME to aaaskills.mydomain.com -> azure website. This is all working fine. Good.
But I want to change the subdomain to skills.mydomain.com, so i updated the existing CNAME to skills.mydomain.com -> azure website. All good.
Now, in my Azure portal i'm trying to add a new hostname for new domain but the azure doesn't recognize the CNAME updated.
Now aaaskills.mydomain.com doesn't work and skills.mydomain.com is bringing up 404 not found and it is suggesting me to update custom domain in azure website.
Am i missing something here?
Domain ownership on azure website was resolved after awverify'ing the sub domain. I added CNAME with records like below to awverify.
CNAME('awverify.subdomain.domain.com','azure website url')
Double check to see if the CNAME and A records are appropriately added in your domain registrar.
Also it take some time for the new host to be reflected in the app's Custom domains page. Try refreshing the browser,Clear the cache and test DNS resolution again.
On a Windows machine, you clear the cache with ipconfig /flushdns.
If the issue still persists, kindly do let us know for further investigation.
I'm trying to verify a custom .ninja domain for a Azure hosted website, but it fails to complete verification. I've completed these steps for several other sites and domains hosted in Azure before and familiar with the awverify CNAME requirement. I've also updated the A record(s) with the Azure provided IP. A ping on the domain name returns the correct IP. It has been close to 48 hours of waiting giving plenty of time for DNS settings to propagate.
Here's the error (I replaced the actual domain with "mydomain"):
A CNAME record pointing from mydomain.ninja to mydomain.azurewebsites.net was not found. Alternative record awverify.mydomain.ninja to awverify.mydomain.azurewebsites.net was not found either.
Are there any restrictions on .ninja domains or those that do not have 3 char extensions maybe? All my other successful attempts with other sites have been on .com domains.
Added an A record for the www prefix, thus having 2 A records. One for # and one for www. Once the www record was added to DNS, verification worked for both www.mydomain.ninja and mydomain.ninja. Odd, but maybe this will help someone else.
Yesterday at about 3pm, I setup awverify records for two website I want to transfer from one Azure account to another. By the end of the day Azure still wasn't allowing me to add my domains, so I took a gamble and re-pointed the domain and www sub-domain to the new IP. This morning of course my sites were down and Azure still won't accept my domains. I've had to point the domain and www sub-domain back to the old IP.
Obviously I'm expecting the response that the awverify CNAME hasn't propagated, but my DNS, and others I checked online, changed within an hour. Why would Azure take 18 hours and counting?
I'm quite sure I've set it up correctly...
I found the answer, though I can't find this documented elsewhere. The cause of the issue is that I was migrating from one Azure account to another. It seems that Azure will not allow two website (even in different accounts) to use the same host names.
Once I deleted the host names from the old account, I was able to add them to the new account.
I can see why this would be the case, but it should be documented somewhere as I can't be the first person to run in to this.
I have an azure website at yis3.azurewebsites.net - I have promoted this to be a "shared" site so that I can use a custom domain. I have the domain yorkshireimagescanning.co.uk that I bought from 123-reg.co.uk. I have configured this to give a CName record with dnsname of "awverify" and destination of awverify.yis3.azurewebsites.net.
I've waited over 12 hours and checked on digwebinterface.com and all looks good but when I click to "Manage custom domains" from the Azure portal , I enter a domain name of "yorkshireimagescanning.co.uk" but it won't accept it.
Please help
* Edit *
I've now waited a couple of days for domain propagation. Here's a screen grab from my domain registrar:
In the azure portal I've tried to add the following custom domains for the yis3.azurewebsites.net site but it won't accept any:
awverify.www.yorkshireimagescanning.co.uk
www.yorkshireimagescanning.co.uk yorkshireimagescanning.co.uk
awverify.yorkshireimagescanning.co.uk
Here's a screen grab from the portal:
To use yorkshireimagescanning.co.uk
To use your domain without the www. prefix you need to add an A Record in addition to the CNAME you've added for "awverify".
First, make sure you've added the domain to the Azure portal by following the instructions under "Set the domain name in management portal" here.
Next, follow the instructions under "Configure an A record for the domain name" on the same page. This involves pointing your domain directly at the IP address of the Azure web site. You should then have added 2 DNS records in total:
CNAME awverify.www awverify.yis3.azurewebsites.net
A xx.xx.xx.xx (your website's IP address)
I've marked the next option as "preferred" because it points your domain at the Azure hostname "yis3.azurewebsites.net" instead of directly at the IP address. The IP address of your Azure website won't change, but if you ever need to deploy your website elsewhere it will have a different IP, so there will be a delay while the DNS change propagates.
To use www.yorkshireimagescanning.co.uk (preferred)
To use your domain with a www. prefix you need to add another CNAME record in addition to the one you've already added.
First, make sure you've added the domain to the Azure portal by following the instructions under "Set the domain name in management portal" here.
Next, follow the instructions under "Configure the CNAME on your domain registrar" on the same page. This involves adding a CNAME that points "www" to your Azure website's hostname (yis3.azurewebsites.net). You should then have added 2 DNS records in total:
CNAME awverify.www awverify.yis3.azurewebsites.net
CNAME www yis3.azurewebsites.net
A note about domain forwarding: Don't use 301 forwarding unless your site has been permanently moved. Use 302 for temporary redirection. More details here.
I finally figured out what was wrong. I was deploying a new version of an existing site but the old version still had www.yorkshireimagescanning.co.uk set on the custom domains page. Once I deleted it then I was able to add the domain on the new azure site.
Good afternoon,
I'm moving the restnet.es domain to host on a Windows Azure Web Site, but it just doesn't work. I guess I made all the configuration correctly, changing the A and CNAME records on the domain register (arsys.es), but the Windows Azure portal doesn't catch it.
The DNS is seted as following: http://www.digwebinterface.com/?hostnames=www.restnet.es&type=&ns=resolver&useresolver=8.8.4.4&nameservers=
As above, it seems is all working, pointing as expected to 137.117.224.218. But when I go into the Portal and set it up, I got this message:
"The DNS record for 'restnet.es' that points to 'restnetes.azurewebsites.net' could not be located. If you want to configure an A record, you must first create a CNAME record with your DNS provider for 'awverify.restnet.es' that points to 'awverify.restnetes.azurewebsites.net'. First allow the resource record to propagate, and then create the A record."
What am I doing wrong? Where is my mistake?
PS: this is the actual configuration:
awverify.restnet.es CNAME
awverify.restnetes.azurewebsites.net
restnet.es A
137.117.224.218
www.restnet.es CNAME
restnetes.azurewebsites.net
Usage
www.restnet.es CNAME restnetes.azurewebsites.net
it is in place, no action needed
Verification
awverify.www.restnet.es CNAME awverify.restnetes.azurewebsites.net
returns nothing, you need to add record above into your DNS
it will take max 48 hours to propagated.