In the current technical preview, Azure lets you create 10 ASP.NET websites. They are given domains such as http://yourappname.azurewebsites.net. Is there currently any way to point a domain name to this website? Or are there any plans to support this in the future?
Update 18-sep-2012: Windows Azure Web Sites tiers:
Free: Allows you to test the Web Site Features
Shared: Cheap hosting (with 5 GB/month free) that supports both CNAMEs, A-Records and naked domains.
Reserved: Same as shared, but you get a dedicated VM
Read all about it in Scott Guthrie's post: Announcing: Great Improvements to Windows Azure Web Sites
Original Answer:
At the moment this is only possible for reserved instances (using a CNAME), this means it's not possible for the free sites you can create (which are shared):
You can only used custom domains in reserved mode. You can’t set a
CNAME like you can in Web Roles because multiple sites share the same
IP address. Switch to reserved mode and set your CNAME in the
configuration and it should work.
http://blog.ntotten.com/2012/06/07/10-things-about-windows-azure-web-sites/
Microsoft confirmed that they will add support shared sites in the future:
https://twitter.com/scottgu/status/210972290719031298
Fast forward two years, it is still not possible to have CNAME directed to Azure free website. The reasons are commercial and not technical. MS says that it is not possible because multiple sites share a same IP. But don't know why I have this dedicated server at GoDaddy that has one IP but hosts 7 different domains :-) So it can't be a technical reason. Of course, if they start allowing it, nobody would want to subscribe to paid versions.
For what it's worth, it's now (finally) available for about $10/month, in shared and Reserved modes). I've tested it and it's working perfectly, after the little DNS dance for the naked domain. This was the missing piece to Azure for some small sites I run.
The Gu has all the info: http://weblogs.asp.net/scottgu/archive/2012/09/17/announcing-great-improvements-to-windows-azure-web-sites.aspx
You will soon be able to use Custom Domain without having to upgrade your plan to RESERVED. We are introducing a new Shared mode. The new Shared mode will have some cost, but it is a lot less than reserved mode, and it will support Custom Domain. Please check back at the http://www.windowsazure.com/en-us/ soon for more info.
As mentioned by Sandrino, this is possible only for reserved instances.
Not sure about Scott Guthrie answer. Check this thread.
It is stated that at this time there is no plans to support custom domains for shared instances.
It also contains a request to comment on Scott's answer.
Update:
It might be available for a fee (same thread)
Related
We have an application that we are hosting in multiple environments in Microsoft Azure. We want to route the traffic based on subdomains, like xxx.mydomain.com should go to the webapp that I have in North Europe and yyy.mydomain.com and zzz.mydomain.com should go to the webapp that I have in the East US.
I know it sounds like simple DNS, but it is more than that. Because:
I need to be able to add or update entries dynamically using code so an API should be available for that.
A normal DNS entry has a 24 hours time to live meaning that if I want to move my app from one environment to another, for up to 24 hours, users will hit both environments.
I expect to have hundreds of thousands of subdomains. Azure DNS has a limit of 25,000 entries.
I've looked into Azure Traffic Manager. It doesn't seem to have an option for traffic based on subdomains.
Also, I've looked at Azure Application Gateway. It seems to be the correct choice and it supports API's, but I cannot find the limits for subdomains.
Any suggestions?
From the criteria, it seems you're looking for a load-balancer/proxy/application-delivery-controller solution that's controllable through an API. I'll add my 5 cents here, as we've just gone through very similar problem. However these are more of a suggestion to look for answers elsewhere then Azure.
Azure
Azure Traffic Manager or Azure Application Gateway have limits which you can't fit in. For example in Azure Application Gateway with 200 rules, you could potentially host only 200 HTTPS site, the moment you need to serve HTTP & HTTPS, you're limited to 100 sites per application gateway. You'd need to split your solution across multiple subscriptions in order to fit subscription wide limits. Also the application gateway API is a bit too convoluted for my liking.
Azure DNS is also a bit problematic, as DNS records can last up to 24 hours. You'd therefore loose the ability to switch/route traffic to a different origin instantly.
Self-hosted
You could look into more old school solutions, run HAProxy or Nginx and programmatically modify their configuration(text files) on the fly and reload the configuration. HAPRoxy also has a socket "API" that can simplify the configuration modification and reload for you.
There's also a new set of service mesh controllers such as Kong, which can run in the cloud natively and are meant for service mesh solutions, however Kong offers a simple API, where you could manage/route traffic easily.
SaaS
If you're into buying this as a Service, Edge Cloud providers such as Cloudflare, Fastly or others are indeed "one big proxy server" and it is possible to configure them programmatically to route traffic to different origins, it's what they do after all.
Azure Application Gateway is indeed perhaps one of the best options for your scenario.
As you already said, it has an api that you could use to dynamically add rules based on your subdomains.
The limits for Application Gateway only allow for 200 rules per gateway.
But you can have 1000 gateways per subscription so if you could chain the gateways, that will give you roughly 200.000 rules.
The Microsoft documentation doesn't show that you can request an increase in these limits but maybe if you ask really nice the might allow it.
Maybe this is not the answer to your question but it might be an answer.
If anyone interested, we've ended up using Azure DNS. We have contacted Microsoft and they confirmed that they can increase the quota to 500,000 which is more than enough for us. :)
I'm a beginner in Node.JS and Mongoose. I have created a small Node.JS app. I have pushed the code into Github and Heroku server. After I have deployed the code into the Heroku server. I have checked my website online. It's working fine. I have used and done some operations in online itself. It has been worked fine, very well.
After One hour I hit my link in google. It's showing This site is blocked due to a security threat. This site is blocked due to a security threat that was discovered by the Cisco Umbrella security researchers. .Why? what is the reason? what happened? what are the steps should I follow. Can anyone help me to work on my app online?
It will really helpful for me. any kind of help would be welcome. Thanks in advance.
Cisco Umbrella will block sites it deems to be a Security Threat to help protect people accessing these sites. This is normally because the site has been associated with one of three activities: malware, phishing, or command and control. If the domain is new then Cisco Umbrella has an option to block new domains for a period of time to protect users against temporary malicious domains.
This protection is achieved when using Cisco Umbrella as a DNS resolvee. This is either done using a client on your device or as a network configuration.
If your certain the domain is safe, you can whitelistthe dmain via the Umbrella Dashboard, if available. Alternativly use another DNS resolver services such as Google which offers no protection or filtering.
For the last couple of weeks, we have been seeing an increasing amount of entries in the web logs of our Azure website whose originating IP address (in the c-ip column of the log) appears to be in the range 100.90.X.X. It has now reached more than half of all the traffic being logged, and is interfering with our ability to perform analytics and threat detection.
According to the Wikipedia entry on reserved IP addresses, this block is part of one "Used for communications between a service provider and its subscribers when using a Carrier-grade NAT, as specified by RFC 6598", so could this be a problem in Azure?
Looking at the logs, the traffic comes from many different user agents (both normal users and the common legitimate bots) and is requesting a broad range of resources, so does not immediately appear suspicious other than the IPs. It looks more like legitimate traffic is being given an incorrect (internal) IP.
It seems to be only affecting static content (e.g. images and XML files), but not ALL static content.
We are using a single Small Standard instance in Western Europe, with a single web app running on it. We are not using any scaling features. There is a linked SQL database, and the website runs primarily over HTTPs. 95%+ of our traffic comes from UK sources. We have not made any changes to logging, which is handled by Azure.
Is there any way that we can return to seeing the actual IPs here, or is this malicious traffic?
It’s possible to alter the logging, but not on an app. The app diagnostic setting is pretty rudimentary — just a switch “to log or not to log?”
What you’ll be interested in is this comparison between apps (it was called “sites” then), roles (available through Cloud Service)1 and virtual machines. The article mentions that there is more control over logging in the roles environment, which I would assume means that you can set up custom logs. This article details how to set up logging for the headers you choose in IIS. Now, you can fiddle with your IIS in a virtual machine, but there is a chance a cut-down version of this would work in a web role, for example. This article discusses how to enable diagnostics logging in your cloud service hosted application.
Moving to cloud service from app environment is not trivial, since you have many more things you must set up. Possibly you’re looking at changing your solution’s structure, maybe altering the architecture of your app. So I wouldn’t consider doing it just so I could see a client’s IP.
The simplest thing you can do is try attaching analytics. There used to be a solution straight from Azure, but I can't find it in the portal. Google analytics is my go-to solution for traffic analysis. It may get you the information you want.
It’s really annoying how Microsoft rebrands an azure service every few months.
I am new to Windows Azure, and from what I have read online it appears that any website hosted in Windows Azure needs to be a .azurewebsites.net website. So, if I had a website www.mysite.com hosted elsewhere, then it seems I cannot host this same site in Windows Azure, since I would have to use mysite.azurewebsites.net as the website url.
Question: Is above fact true? I could not find any documentation or any online article on this.
You can certainly host your own domain using Azure, as detailed in this support article (which links to a walk-through).
You can bind your domain to a website or cloud service, just I believe this is only something available in a paid tier. (Follow-up: Using a domain is only available in Shared, Basic or Standard mode.)
No, this is not true. You can have other domains, but in the background it will always has a .azurewebsites.net. See my blog as an example: http://www.buzzfrog.se. (This is only an example of the hosting.)
Here is an article how to do it: https://azure.microsoft.com/documentation/articles/web-sites-custom-domain-name/
/dag
I was wondering whether or not Windows Azure is a viable option, now that they offer 10 free websites, for hosting a simple website with a database and domain name etc.. or is more traditional web hosting still the better option?
The database won't be that big, so the $5 for the 100MB database option will be plenty. I guess a few dollar's would be needed for traffic too?
Custom domain names can only be used in Shared or Reserved modes which are not free.
The free websites would be under [yourSubdomain].azurewebsites.net
So, it depends whether having your own domain matters to you and, if so, whether you are willing to pay for the website.
Notwithstanding this, Azure websites is a perfectly good cloud solution offering quick deployment of numerous CMS systems including WordPress, Joomla, etc.
I think it is a viable option. However, to get your own domain name you must change the website from free to shared or reserved mode. Heres description and link how to do this!
"When you create a web site, Windows Azure provides a friendly
subdomain on the azurewebsites.net domain so your users can access
your web site using a URL like http://.azurewebsites.net.
However, if you configure your web sites for shared or reserved mode,
you can map your web site to your own domain name."
http://www.windowsazure.com/en-us/develop/net/common-tasks/custom-dns-web-site/