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
Related
everyone.
I recently bought a domain on azure and I can't bind it to an app service (web app).
When I try to bind a domain it says "App Service Domain is in a broken state. Please navigate to the App Service Domain resource and delegate to Azure DNS before adding hostname."
When navigating to the domain at https://resources.azure.com, it looks my dnsZoneId is assigned to another resource group and I don't know how to change it.
I tried to delete the DNS zone and recreate it but I can't bind the dns back from https://dcc.secureserver.net
Can Anyone help me please?
Thanks in advance
Newest
About how to change your dnsZoneId to another resource group, you can read this post. I think it useful to you.
PRIVIOUS
Under normal circumstances, this problem does not occur, because when you successfully purchase a domain in azure, all information and services of the domain name are hosted on azure.
There is a similar case here, you can refer to it. May be helpful to you.
If there is a problem, I guess the reason is:
Some of your misoperations may cause the domain name service or settings to be configured incorrectly, making it unusable. (This probability is relatively low)
It may be the domain management service of azure, there may be a problem in your region. It may take a while to try again, or transfer the domain name to godaddy for management. (The reason for this is because I have encountered it in godaddy before, but it was solved after migrating the domain name to Tecent in China)
If the above operations have been tried and cannot be solved, please raise a ticket in the portal for help.
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 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.
In the next several months we will be going live with a web app ('MyApp') that is being hosted on Azure. We have purchased the MyApp.com domain and our Azure domain name is MyApp.azurewebsites.net.
We do not want our users to ever see the azure domain name in any form. We want them to see www.MyApp.com or www.MyApp.com/Sales/ViewSale etc.
I think I know how to map www.MyApp.com to MyApp.azurewebsites.net based on this article. We won't be able to set this up for a while, so I'd like to know what the user will see in their browser URL when they go to www.MyApp.com. Will they see www.MyApp.com or MyApp.azurewebsites.net? And then what will they see as they navigate various pages in the app?
Your azure website needs to be at least at the 'shared' level. This is the first tier of 'paid' azure website hosting. You do this under website > scale.
app service plan pricing tier = shared.
then you would choose 'configure' and look for 'domains' and add your www.myapp.com domain.
Then you head out to your DNS manager and add a CNAME record that directs traffic from www.myapp.com to myapp.azurewebsites.com, OR you can lookup up the Virtual (public) IP of your azure website and update the A record in your DNS manager.
Either route, your visitors will see www.myapp.com/mypage, www.myapp.com/mypage2, etc.
Once you have the proper hosting level (the control panel will tell you, look for custom domains) and configuration, they can access it as www.myapp.com. You may need to provide your own SSL cert in order to configure it as well.
When it comes time to SSL, check out this post (Azure SSL Certificate) that I made regarding uploading of SSL certs in the control panel. It will save you a headache.
The article you linked appears to have solid information based upon my recent experiences. One thing to note: It has screen shots from the old configuration panel, so some things may look different in the new one.
I haven't found a way to hide the myapp.azurewebsites.com method to access a page, other than maybe doing a redirect inside your code. However, until you have your DNS setup it might be nice to see things working under that domain to start.
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.