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 –
Related
I'm after having associated a custom domain for firebase hosting and firebase dynamic links, I was trying to setup a custom domain for authentificatio email templates. However verification for the authentification fail.
I'm using Namecheap for the DNS configuration.
Is it because the cname and # directive conflict one with each other ? I chose a subdomain for the authentification template mail:
Information is DNS servers is public information. Trying to answer what is wrong is very hard when you hide the information required.
Go to Google Domains Is your domain verified in Google Domains? If not complete that step first.
The CNAME resource records appear correct.
Most likely the last two TXT records are wrong. I am guessing that you are using something like app.example.com. The managed zone is example.com. The host is app. Your TXT records should only have *app without the managed zone example.com.
After you modify DNS server resource records be prepared to wait. Firebase will say up to 48 hours.
If my answer does not solve your problem you will either need to disclose your DNS server resource records or find someone that understands DNS to help you.
the company I’m working for provided me a subdomain. test.mycomp.com . I want to add it to my azure web app via custom domain.
The azure system recommends a CNAME delegation and provided me the information to enter web-zeudz-staging.azurewebsites.net in the dns management as CNAME.
After doing so and verifiying via DNS Lookup, Azure always gives me „Domain Ownership Error“. What can I do to make this work?
Is your DNS provider also a CDN provider, for example cloudflare? If so, turn off the CDN/proxy function so it's a DNS only record and try again.
If you don't have any control over the CDN function you can use txt record validation.
Create your TXT record awverify.subdomain.test.mycomp.com with value web-zeudz-staging.azurewebsites.net and validate again. It should succeed.
There's also a CNAME awverify method but you need CDN disabled for that too.
I find it strange that your company doesn't have the option to enable/disabled CDN for any given DNS entry though.
I have an Azure SendGrid account that works great. I can send e-mails no problem with the usual API. I need to setup Sender Authentication (2 reasons, first it will help with receiver finding it in their junk and more importantly it will allow me to setup an Inbound Parse).
I have consulted the Sendgrid Documentation (https://sendgrid.com/docs/User_Guide/Settings/Sender_authentication/How_to_set_up_domain_authentication.html), which has explicit instructions, which involve DNS Records (more soon), but unfortunately this isn't working. I have also gone through their troubleshooting. I think it may be an issue with my domain actually being a sub-domain, but I can't figure out how to fix the DNS records to make it work.
I have a "DNS Zone" setup for my site, lets call the site "fake.azurewebsites.net".
Sendgrid instructed me to add the following CNAME records (numbers are scrambled):
em1879.fake.azurewebsites.net > u7381760.wl261.sendgrid.net
(..as well as two others)
So I made those records, and waited over 48 hours for DNS refresh, but Sendgrid will still not verify. I get the error: Expected CNAME for "em1879.fake.azurewebsites.net" to match "u7381760.wl261.sendgrid.net". I also tried their troubleshooting and wasn't able to get an "answer" using the DIG command. I am not using whitelisting or any of the other features that are known to interfere.
In all the documentation, the records usually take the form:
em1879.usersDomain.com and not em1879.userSub.Domain.com, so that could be part of the issue, but I could of course be missing something.
I wanted to copy the answer that I got from Microsoft Tech support. Based on #mdeora comment, I contacted Azure and below was the response. It seems that the SubDomain is the problem, but only specifically for these azurewebsites.net subdomains, it may work fine for other subdomains if you can setup delegation.
"I suspect a delegation issue.
As I understand it, you have created a DNS zone name 'geic.azurewebsites.net'. This has been assigned name servers in Azure DNS (e.g. ns1-08.azure-dns.com etc). You have then created a DNS entry 'em8849' of type CNAME.
The problem is that there is no DNS delegation in place from the parent DNS zone to your DNS zone. In this case, the parent DNS zone is 'azurewebsites.net'. This is owned by Microsoft, and they do not support customers setting up delegations from this domain.
You should:
Purchase your own domain name (e.g. myapp.com). You can do this using the App Service Domains service in Azure (currently in Preview). See https://azure.microsoft.com/blog/app-service-domain/
Create a corresponding DNS zone in Azure DNS
Set up DNS delegation for your DNS zone. See https://learn.microsoft.com/azure/dns/dns-delegate-domain-azure-dns
Create your DNS record. For a Web App, use either a CNAME to the 'xxx.azurewebsites.net' or an A record directly to the site IP address.
For Web Apps, you will also have to register your domain name as a custom domain for the Web App. See https://learn.microsoft.com/azure/app-service/web-sites-traffic-manager-custom-domain-name
If you use App Service Domains to complete step 1, then steps 2 and 3 should be completed for you, automatically.
Good luck!
Jonathan (www.opsgility.com)"
Proposed as answer by Jonathan TulianiModerator Friday, June 15, 2018 9:00 AM
For me, the problem was that Azure automatically includes domain name in the records: Sendgrid asks to add a CNAME record "s1.domainkey.yourcustomdomain.com"; You shoudn't include ".yourcustomdomain.com" in the name because azure automatically includes it. You can check that by editing a record and seeing that it ends up as: "s1.domainkey.yourcustomdomain.com.yourcustomdomain.com". So the record should be only: "s1.domainkey";
It worked for me, but i have a custom domain acquired from azure; maybe it works for azurewebsites subdomains, i'm not sure.
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.
For the last two days I've been unable to create a CNAME from my domain to my blob storage account. I've registered the domain and added a CNAME that points to verify.azure.com on my DNS settings, but whenever I validate it (even after waiting a few hours), it never seems to validate... the error I get the Azure portal is "An unexpected error occurred while validating the domain name. Try again later."
Are there some issues going on?
verify.azure.com will only authenticate that you have the proper key to your domain however you would need another alias to set the proper CNAME configuration. Based on what you have written above you are pointing your host to verify.azure.com, however have you setup your storage subdomain alias to your storage name as well? If you have setup both the entries correctly, and still see the problem, at your domain registrar level there are some logs available which you can request for further troubleshooting.
Get more info here and here.