Azure is not seeing the CNAME pointing to awverify.mysite.azurewebsites.net.
I'm wondering if because I added the A record at the same time as the awverify CNAME Azure is having problems seeing the CNAME.
Here were my setup steps:
Created A record pointing to Azure's provided IP
Created CNAME with awverify.mysite.com to awverify.mysite.azurewebsites.net
Tried to add custom domain in Azure's domain manager
failed ಠ_ಠ
Azure would could not find the CNAME for awverify.mysite.com after 24 hours of trying.
One thing that was funky was when using the site http://viewdns.info/dnsrecord/?domain=mysite.com it never showed the CNAMEs. Not sure why.
Related
I have a web app deployed on Azure and I'm trying to make it so both <myurl>.com and www.<myurl>.com work. Right now I have both domains listed on Azure within my webapp. www.<myurl>.com is registered as a CNAME from www to <myurl>.azurewebsites.net in godaddy. I have an A record from # to the IP address shown by Azure, as well as a TXT record from # to the given DNS by Azure <myurl>.azurewebsites.net
The problem is when I go to http://<myurl>.com it will change the URL to <myurl>.azurewebsites.net but when I go to http://www.<myurl>.com the URL is does not change.
Below are my go daddy DNS records. Most of these were there when I bought the domain so I'm not sure what they do. There is an A record that I can't seem to edit and I don't know what that IP address belongs to either.
Alot of this can be done with an A and a CNAME. You will need to add both "www" and "awverify.www" in your DNS, and do those corresponding entries in the Azure portal.
Here's good doc:
https://blogs.msdn.microsoft.com/kaushal/2013/07/05/azure-app-service-how-to-configure-a-custom-domain/
Here's alot more details:
https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-domain
The Azure portal will also give clues on what to do.
We are trying to migrate sites from AWS to Azure WebApps.
AS IS:
The CNAME of the existing site points to Imperva. Imperva then points to AWS Site.
TO BE:
The CNAME of the existing site points to Imperva. Imperva then points to Azure WebApp Site.
PROBLEM:
When I try to add the custom domain to azure Web Apps website, it complains with the error that the existing Site MUST have CNAME pointing to Azure Website.
see example below:
This means that as part of cutover, we need to do below:
1. Quicky update CNAME to point to azure web app
2. Once custom domain is setup in azure
3. Change the CNAME back to Imperva.
This sounds bit hacky.
Is above right approach or am I missing anything here?
The part that you're missing is the direction of the CNAME. What Azure wants to do is to ensure that you do actually have authority over that domain name. So they want you to create a CNAME that points from awverify.www.example.com to www.example.com
Once that record is created Azure will looking that record and ensure that it redirects to www.example.com. This has no impact on any existing configuration (unless you just happen to have awverify sub domain in uswe already!)
www.example.com will still work in exactly the same way as before until you are ready to move that name to Azure.
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.
I have set up A and CNAME records. When I go to manage domains in the azure portal I enter alqalam.tv and www.alqalam.tv (my domain). The page shows that it has verified but when I save it shows an error. I have tried storage custom domain but it doesn't even verify.
My Azure website subdomain is alqalam.azurewebsites.net
I have made DNS lookup: http://www.hscripts.com/tools/HDNT/dns-record.php
and it shows
Domain Type Class Result
www.alqalam.tv. CNAME IN Alqalam.azurewebsites.net.
alqalam.tv. A IN 94.245.104.73
thank you
this did it for me:
Type Host Answer TTL
A alqalam.tv 94.245.104.73 300
CNAME www.alqalam.tv alqalam.azurewebsites.net 300
CNAME awverify.alqalam.tv awverify.alqalam.azurewebsites.net 300
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.