If I want, I could buy a new domain and point to something.azurewebsites.net. No Registrar imposes a barrier here...
My question is:
will it work? or the owner of something.azurewebsites.net has to explicitally do some configuration?
What if I point to the current IP (or the now possible, fixed IP) of something.azurewebsites.net?
Details:
I don't own a domain neither want to buy one just for testing this, or i would...
http://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/ should answer your question. In short, yes, the owner of something.azurewebsites.net has to setup a verification entry in the Azure management portal.
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.
Is it possible to have an App Service respond to all domain names that it receives? I would really like to be able to deploy to an App Service plan, rather than a VM. Note I am not trying to do wildcard subdomains - these require adding them through the Azure console. I am trying to accept any domain name that the app service receives. Adding and verifying each domain is not practical.
I have a multitenant app, so this is really important to me so that customers can use their own domain names.
I've tried adding the domain * and ., but it fails validation.
I don't think you can do this because Azure requires validation of domain ownership by adding specific records to DNS. Here is a discussion as to why they do that.
The best you might be able to do is to automate or script the binding, but even then you would need assistance from your third party partners/customers to verify their DNS ownership.
An alternative would be to transfer your DNS to Azure and use subdomains. I know you've said you're not looking at that solution, but using the Azure DNS offering would allow you to fully script out the onboarding process for a new customer.
Could you ensure that the changes to your DNS settings have been confirmed and validated from your DNS provider’s end. For certain providers, such as GoDaddy, changes to DNS records don't become effective until you select a separate Save Changes link.
For more details, refer "Map an existing custom DNS name to Azure Web Apps".
You may refer MSDN thread, which addresses similar issue.
This question is sort of dev ops or networking related. When I point a domain at a hosting provider, I use a fairly generic Nameserver, i.e. ns1.digitalocean.com.
I understand when I add a domain to my hosting service to manage, that the hosting service recognises I am the registrant and serves up the site to the domain - so my question is, if another customer of the same hosting service adds my exact domain to manage on his account (there are now two) how does the correct registrant of the domain get selected? I.e. if there are two accounts on Digitalocean and they both put in example.com to manage and the registrar of example.com is pointing to the generic ns1.digitalocean.com how does Digitalocean select the correct accounut and code base to serve up? Apologies if any confusion or lack terminology - I am a bit fuzzy on this whole process. Thanks, Nick
They wouldn't allow another user to add the same domain, otherwise it's a bug.
We're thinking of changing our web hosting plan mode from Shared to Standard but are not sure what will happen with the dns registrations I've set up for my sites. Would a move result in a new ip-adress forcing me into changing all my dns-registrations?
If you are using a custom domain (e.g. www.yourdomain.com) and pointing that via a cname to the actual Azure url (e.g. yourproject.azurewebsites.net) then you shouldn't need to change your dns. If you are pointing to an IP then you may have to change your dns.
Really depends on how you have setup your dns currently, could you elaborate on the records you have?
There is a good article on the Azure help area discussing this very topic:
http://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
Check out the 'CNAME or Alias record' section in particular.
Use CNAME records instead. That way you don't have to worry about it.
Sorry if this question is very elementary. I've registered on iPOWER my new domain, however I don't know how to connect my hosting to my domain on register.com.
If anyone uses the two sites detailed instruction would be great. Otherwise maybe there are some steps that have to be taken between any two hosting and domain services that I am missing out on.
In register.com account management page:
Click your domain
In the domain management page, go to last section ADVANCED TECHNICAL SETTINGS
You can customise your CNAME records there. e.g. pointing *.yoursite.com to example.iPower.com
according to this page, it may take 12-24 hours to update.
Hope that helps.