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.
Related
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 was attempting to do something else and obviously did not know that the "Delegate to Azure DNS Zone" would break my site. Because after I clicked the button, my site no longer can be displayed. I immediately removed this but it is still unable to be displayed. Can anyone fill me in on what I need to do to make this work again? Happy to provide more information just not sure what else you may need to help. I purchased the domain through Azure about a year ago.
If I understand correctly, you bought the domain one year ago and your domain is hosted by GoDaddy(your domain registrar, where you bought domain through Azure portal). It means requests to your site is resolved by name servers provided by GoDaddy after then.
When you use "Delegate to Azure DNS", those name servers will be replaced by ones provided by Azure. (If you didn't do any similar settings except clicking one button, that means operations are finished through one click.)
So your site is lost for the moment due to the change of name servers. As #juunas said, DNS propagation may take some time(Up to 48h but usually faster).
You may also need to check, whether your DNS record in DNS Zones and your Hostname bindings are changed or removed by the delegation operation.
Hope it helps.
If the problem can't be solved, you can show us:
Where is the button on your site
How do you remove this settings
DNS records and hostname bindings
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.
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'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.