I have deployed a installation of DNN in Azure and registered custom domain CNAME to point at the DNN install and the sites which are registered in the CMS; however azure is reporting the site is not present?
can anyone help please?
It sounds like you might need to configure the custom domain name in Azure.
See section Point your Domain Names at Azure Websites
You may need to upgrade your DNN installation from FREE to Shared (or higher) in the Azure portal before you can manage the domain. This is explained in the above link.
And here's official info on adding custom domains to Azure: https://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
Related
Our websites in the west us region are not available. We're trying to access them using our custom domain but we can't access.
When we are using azure website default domain(.azurewebsites.net), we can access our websites. All websites domain configuration and dns redirection are correct. Is there a problem caused by Azure?
I understand that you are able to access Azure Website using but you are unable to access the same using Custom Domain
<WebsiteName>.azurewebsites.net
You might want to re-check the steps followed in creating Custom Domain by following the below link
http://azure.microsoft.com/en-us/documentation/articles/web-sites-custom-domain-name/
I bought a domain through azure portal but i can't find any file manage option for my domain and there is no option to manage mail account. I want to know if there is any portal like CPANEL or something similar for domain managing?
There is no cPanel like hosting admin in Microsoft Azure Web Apps.
cPanel is a hosting platform used by shared hosting providers such as GoDaddy or HostGator. Microsoft Azure is a cloud hosting platform in which you manage your cloud as if it where your server. You have to manually go in and setup your web apps, virtual machines etc.
If you want to use cPanel you could always spin up a Linux VM and then install cPanel on it. This will give you full control like with the other providers.
Hope this helps. Feel free to reach out to me with any questions!
I have a multi-site application running on Azure Websites. When a user signs up, they pick a name for their application and they end up with "appname.coolapplication.com". Everything so far is working great within our own domain.
Our application needs to allow users to enter their own custom domain. For example, they want to view their application from "elsewhere.com" rather than "appname.coolapplication.com". How do I go about configuring Azure Websites to allow me to do this?
You don't. Per these instructions you instruct the customer to enter a CNAME record on their domain registrar for the Azure domain, and then it begins to work.
EDIT:
The CNAME only "just works" for Azure Cloud Apps. For Azure Websites, it turns out you must add the domain in the portal as well. I'd thus recommend switching your Azure Websites to Azure Cloud Apps to simplify the issue.
You can use the powershell api to add custom hostnames.
See this question for details: Add many domains to an azure web site
I am trying to create a multitenant Azure website which is a way for people to sign up and get their sub-domains. I have followed the instructions in here (http://www.stratospher.es/blog/post/wildcard-subdomains-in-windows-azure) and manage to get all *.mydomain.com CNAME to mydomain.azurewebsites.net according to (http://www.digwebinterface.com/)
Here is the problem
if I go to tenant1.mydomain.com I'll get the 404 server error. However if I log in to Azure and go to my website Manage custom domains and add the tenant1.mydomain.com then everything would work fine.
The idea behind the wildcard is I can add tenant pragmatically/dynamically. Is there anyway to automated this process or add a wildcard in the azure Manage custom domains. Is there any difference between app cloud service and website?
Thanks for your help
Update
I end up using cloud services instead of websites. You don't need to configure the custom domain names in the control panel anymore. Just simply point cname and your good to go.
Did you check out the use of Amazon Route 53 to configure the domain mapping in Azure, it seems that there are options.
Please refer the following links
Sub domain mapping in windows azure
Add custom Domain to azurewebsite
I've looked at all related posts in MSDN and stack overflow but still having difficulty finding a solution.
I am looking to map a domain and all sub-domains to my windows azure website. It is a reserved website instance. I am using Amazon Route 53 DNS manager and have mapped a wildcard CNAME to my azure sub domain, and created a redirect on the naked domain to the www. subdomain.
When I navigate to the naked root, the redirect kicks in and I'm brought to www..com, where I receive a 404 error from azure.
I know the wildcard CNAME is working. I've verified using MXToolbox. If I go to "Manage Domains" in the Azure web UI admin system, I can manually add "www..com" or any other subdomain (e.g. "helloworld..com"). Azure verifies it fine and after saving, I can pull up the website fine by navigating to that subdomain and my azure website loads.
Is there any way to add wild card subdomains without having to verify each one manually through the azure ui interface? My application is a SaaS that relies on custom user sub-domains to serve up their branded website and gain access to their account so I need any and all subdomains to map to my application.
Currently, wildcard domains are not supported as far as I know. At least on Windows Azure Web Sites. They are on the roadmap, but currently you'll have to rely on adding every domain manually.
See wildcard comment on "Configuring a custom domain name for a Windows Azure web site".
Another feature not yet available on Azure Web Sites is SSL using a vanity (your own) domain name. If you want full control of your site(s) you can use Azure Cloud Services instead of Web Sites. With Cloud Services you can provision certificates, domain names, and run multiple sites on the same instances using host header routing.
Anything you can do with IIS Management you can do with a cloud service.
You're a little closer to the metal compared to Azure Web Sites (but not as close as with a VM) and you get load balancing, scaling, caching, and other goodness. Visual Studio 2010/2012 has excellent deployment tooling. You will need to study up on Azure deployment projects from VS, bit it's not bad.