I've set up my first site on Azure. Let's call it 'mysite.org.uk'. I've uploaded the files to Azure as a shared Azure website. It's accessible at 'mysite.azurewebsites.net'. Now I want to test it out by pointing a live subdomain to it, so basically I want it to resolve with the URL 'cloud.mysite.org.uk'. I've read the documentation and it says that before I can add an A record to my domain to do this, I need to create a CNAME record. The instructions it gives are:
The DNS record for 'cloud.mysite.org.uk' that points to
'mysite.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.cloud.mysite.org.uk' that points to
'awverify.mysite.azurewebsites.net'. First allow the
resource record to propagate, and then create the A record.
Okay, so I've logged into the Plesk control panel of the current host (where the DNS is controlled) and added a CNAME record with 'host': awverify.www.mysite.org.uk. and 'value': awverify.mysite.azurewebsites.net. I did this more than 24 hours ago so it should have propagated by now, but when I try to add the domain in the Azure portal it still tells me there's no verification CNAME record. Similarly when I ping awverify.www.mysite.org.uk it doesn't resolve (surely it should if it's set up right, as it's a new record, so it shouldn't rely on DNS propagation time?).
To be on the safe side I've also created a CNAME with host: awverify.cloud.mysite.org.uk and value: awverify.mysite.azurewebsites.net and that too isn't working. In fact when I add these CNAME records Plesk tells me:
Unable to resolve the canonical name
awverify.mysite.azurewebsites.net.
Anyhow, I'm a little bit stuck. I thought I'd followed the documentation pretty closely but obviously something isn't right.
If anyone has any pointers I'd be most grateful.
Thanks
It must have been a propagation issue oddly, as 48 hours later it works when I add the domain to Azure.
Related
Error creating Custom Domain in Azure
Hi, I am trying to link a custom domain to my static website that is located on my blob storage account. When creating the custom domain these are the azure instructions "Create a CNAME record with the DNS provider that points the domain (eg, www.contoso.com) to blobstorage.blob.core.windows.net or blobstorage.z13 .web.core.windows.net and then specify your domain. This method is simpler, but causes a short downtime while Azure checks the domain registration. "
In my godaddy account I have created a new CNAME record as follows Type: CNAME, name: www.mydomain.com, value: blobstorage.z13.web.core.windows.net.Y when trying to specify the custom domain in azure (mydomain.com) generates the following error: "Could not update storage account 'XXXX'. Error: The custom domain name could not be verified. CNAME mapping from mydomain.com to any of ..... does not exist "
I do not understand what I am doing wrong, I am very new in the subject and I really appreciate the help you can give me. Thank you very much
Be sure you have the CNAME record set correctly in the DNS settings for your domain name, then give it some time to update. DNS doesn't update immediately, it can take some time for the update to sync through all the DNS server between your registrar and Azure or your local ISP. This is especially the case when you test and it fails, then you need to wait at minimum the TTL (time-to-live) time that is set on the DNS records updated before you'll be able to test again.
On an aside, I'd recommend setting the TTL on the DNS records to 1/2 hour, then when everything's working you can go update it to a longer TTL. This will help when you need to update things and retest again to get it working.
I could already make the configuration I was looking for by configuring a CDN. this is the link learn.microsoft.com/en-us/azure/storage/blobs/… Thanks everybody fot your answers and comments –
I am trying to set up a secondary azure website in a different subscription.
When creating the Custom Hostname for the new site location, I am forced to validate the hostname.
Azure complains that the hostname is registered against a different CNAME and prevents me from adding it.
This is true, but I don't care, I want this to swap over from the old website to
the new one when the DNS records propagate.
I the old IIS world, I'd have just added the hostname to two servers and when the dns pointed to the correct one, it worked.
Now in Azure it validates that the Azure Hostname I am pointing it to is correct and that the cname record already exists, it isn't 'valid' until I change the DNS.
I have to disassociate the current cname, then add to my new site.
I'm sure the only issue here is the "validation", there is no reason why I can't have the name in two places, dns decides which it goes to, not the end point web site.
I'd like to be able to set this alias, whether valid or not, so that when it becomes valid, it works.
The result I get is validation prevent me adding the hostname.
- I have to ask the client to change the DNS Record
- when they manage to do that, they will tell me
- only then I can go in to Azure and add the hostname to make my site work.
There is documentation for this exact scenario: https://learn.microsoft.com/en-us/azure/app-service/app-service-custom-domain-name-migrate
You can create a TXT record with host:
awverify.register.tourofmargaretriver.com
and value:
cyclingeventuresregistration-production-webapp.azurewebsites.net
This verifies domain ownership without directing traffic to it.
I managed to get my custom subdomain name assigned to my Azure website, following this (very carefully):
link to azure custom domain name instructions
Is it necessary to keep the "awverify" DNS records after the custom domain names linkage has been established?
I deleted the awverify DNS record for the test subdomain, and was able to add another subdomain pointer to my azurewebsites test site.
Maybe I did not wait long enough. Does anyone else have any experience with this, to say one way or the other?
Not sure if I understand the issue you are running into... but the CNAME entry with the 'awverify' subdomain is used to "prove" to Azure that you own that domain when you are wiring up a custom domain name. Once that is established, you no longer need that.
I did the following steps but my domain was not getting resolved:
I created a zone (file) in Google Cloud -> Networking -> Cloud DNS using the right DNS name for the domain.
I put these NS as shown in Registrar Setup into my domain registrar:
ns-cloud-c1.googledomains.com
ns-cloud-c2.googledomains.com
ns-cloud-c3.googledomains.com
ns-cloud-c4.googledomains.com
I waited hours until the NS changes kicked in and verified in whois.
My domain was getting resolved.
Did I miss any other steps? I could not figure out so that I abandoned the Google Cloud DNS and went with my registrar's DNS and it is working now.
Make sure everything is spelled correctly.
i had trouble the other day. getting the domain to resolve while using google cloud services dns.
after waiting for about 30 hours, i double checked my work and found out that i had misspelled my domain name when i set up the dns zone.
usually the google dns entries resolve pretty quickly, especially if the domain is purchased from domains.google.com
the trailing . at the end has not been necessary for me. infact, when using domains.google.com, the trailing dot is automatically removed when entered as the custom dns-server.
All the NS you have listed doesn't have trailing . towards the end, as in
ns-cloud-c1.googledomains.com.
Would you be able to try updating the NS with your Registrar?
Have you already add a record (A record) to map the external IP address to your domain?
Your domain should be already working if you have all the records that are needed (and properly copied the NS record to your domain provider). However, for some time, you may need to wait for the propagation to change. See this link: https://cloud.google.com/dns/docs/overview#propagation_of_changes
In Google Cloud Platform, Cloud DNS has two requirements and I think you forgot the "A" record.
Requirements:
domain name from your domain name registrar.
IP address to point the A record of your zone. A valid IP address can be a server you already have running with an IP address you can point to.
To create an "A" record check below link:
https://cloud.google.com/dns/docs/quickstart#create_a_new_record
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.