Provide DNS Services for my domains and sub-domains
DNS is crucial - if it's down, my Azure web roles are down. I don't trust GoDaddy and Verisign with my production DNS, so I either need to have on-premise load balanced DNS servers or pay someone to do it. It would be great if Windows Azure took care of this for me.
Azure DNS is now Generally Available, see https://azure.microsoft.com/blog/azure-dns-general-availability/ for the announcement blog post.
Thank you for your feedback and please continue to submit your suggestions and vote for others.
Tim Sneath commented
This is awesome news. I'm excited to use this and switch over my existing domains to Azure.
Any idea when Azure DNS is going to be released for production use? Is it currently supported to use Azure DNS for secondary zones (at least before it is out of preview)?
We really need to be able to user naked domains with Traffic Manager. Our customers require both features, and we are unable to set CNAMEs at the root of a domain. It would make sense for Traffic Manager to support A records.
Hi Azure network team,
To echo Chris Polewiak's comment, it would be great if you would also undertake acting as the domain name registrar so I can move my entire DNS management to Microsoft Azure. Splitting management of the authoritative records of my domain and the DNS management downstream of that seems like extra work, especially as we are using DNSSEC which would required co-ordinated changes periodically between the two parts of the DNS management solution.
Sadly, I won't be looking to move our DNS management over to Azure until it can manage all DNS elements.
Emmanuel Huna commented
Thank you "Azure Networking Team" for the update! For those that didn't see it, Azure now supports a DNS domain hosting service, see http://azure.microsoft.com/en-us/services/dns/
Chris Polewiak commented
Good information - but what if I want to still have Primary DNS (Authoritative), and use Azure DNS only as Secondary (also Authoritative).
Let's just say that I can't get rid of DNS management from my servers.
Jason Penniman commented
This is a must, and should play well with Traffic Manager. Maybe we need to request a separate enhancement request for Traffic Manager to allow static IP address for its *.trafficmanager.net addresses. Like other in this post, I've had to refer clients to AWS Route 53 as a cloud-based traffic failover solution because traffic manager only works with cnames.
+1 to this request, as Traffic Manager in its current form is not really useful.
We have a naked domain, like most startups these days and that could not be configured.
Setting CNAME on your root website is not a good idea for many reasons. In addition avoiding having many CNAME records improves performance.
So the best course of action is to have DNS management done within Traffic Manager and use A record instead of CNAME
We are we not competing here yet....
Dear Amazon Route 53 Customer,
Today we are introducing several new Amazon Route 53 features: integration with AWS CloudTrail, tagging for hosted zones and domains, health check status column, and one-click health check alarms. You can now use AWS CloudTrail to record and log Route 53 API calls. Using CloudTrail, customers can get a history of their Route 53 API calls made via the AWS Management Console, AWS SDKs, command line tools, and higher-level AWS services (such as AWS CloudFormation). The AWS API call history produced by CloudTrail enables security analysis, resource change tracking, and compliance auditing. Please reference the CloudTrail product page for more information on how to get started.
Arthur Markus commented
I'd like to see an "Amazon Route53"-like dns service offered by Microsoft Azure!
I can't quite believe that this has been requested in 2009, and we are in 2015 and we still do not have this service. I'm being forced to continue using Amazon AWS for this...
Any updates on this?
[Deleted User] commented
This seems like a big gap in the Azure offering, especially seeing as AWS has had something like this for a while now. It should support managing a wide set of record types, import/export configuration, webhop, etc. It would be nice to see the product split (priced) into different offerings based upon needs. eg., from Personal/Testing/Development with normal availability/ redundancy all the way up to Mission Critical with the highest availability and global redundancy/ failover.
Would it be possible to get an update on this request? With all the latest releases and new portal look, integrating DNS services would be really nice:)
mick delaney commented
Any further information regarding this issue.
Gyan Ojha commented
The optimal speed can be achieved by the compression of traffic and by minimizing server loads. Web acceleration will enable you bring about a drastic improvement in the web page response time. This kind of acceleration usually come in lesser costs and offers the best web application performance.
Gyan Ojha commented
The optimal speed can be achieved by the compression of traffic and by minimizing server loads. Web acceleration will enable you bring about a drastic improvement in the web page response time. This kind of acceleration usually come in lesser costs and offers the best web application performance www.cotendo.com.
Pete @ Philtinium commented
We've been using dnsazure.com which has done a superb job of handling our A records dynamically for our site soundtracktoyour.com. Still it would be useful if as part of the Azure platform that these services were offered too.
This can be done in a VM role. But it should really be built into the azure services
This seems like a really obvious gap in the Azure service, which ought to be filled by the Azure product.
Until there is a proper Azure Dynamic DNS service in place for the musical IP/hostname issues, then the Azure platform can not possibly be considered to be an "enterprise" solution.
We already have a commercial/billing relationship and defined SLAs with Azure, so it makes absolutely no sense to add a 3rd party DDNS provider into the mix.