How can we improve Azure Networking?

← Networking

Azure should be its own domain registrar

Windows Azure should offer domain registrar services so users don't have to maintain our domain names with a separate company. This also has the potential to greatly streamline the process of setting up a website on Azure.

1,230 votes
Vote
Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
che shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

42 comments

Sign in
(thinking…)
Sign in with: Microsoft
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • che commented  ·   ·  Flag as inappropriate

    This is the biggest gap with other public clouds. Please let up buy and host our domains in Azure.

  • John C commented  ·   ·  Flag as inappropriate

    It would be nice to have a streamlined user experience that asks for all the needed info to activate a static Azure website, instead of having to go to this page here, then another page over there, etc. We already have to wait up to 48 hours to see if it all works (can use DNS checker sites, I know). Just one page, and when done, a confirmation that Azure has all the info it needs to turn the site on when DNS records are replicated.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please consider making domain registration available there is just to much back and forth between the Third Party Azure to gte this to work propperly and thx

  • Eric-ITaaS commented  ·   ·  Flag as inappropriate

    Agree, would very much like to keep this in Azure instead of going to a registrar. Is there a way to transfer domains into Azure? All the transfer solutions/options are 2+ years old and the comments indicate that they no longer work.

  • BenTheBuilder commented  ·   ·  Flag as inappropriate

    While I appreciate this is under review.. This is a huge miss for Azure as all other Public Clouds offer this service.

  • Bluetech commented  ·   ·  Flag as inappropriate

    To be honest, this would be handy, but so far down the list of essential requirements. Considering such a tiny portion of the world is using a .com domain. There's so many different countries gTLD registries that they would need to sign up with as a registrar to offer this service and so much existing competition in the market as it is.
    I question really why this should be prioritised over some of the other far more important items on their todo list like zone transfers and the more essential security requirements of enabling DNSSEC that so many companies and country governments now have policies requiring their DNS zones to be enabled.
    So value for moneywise as a business, this should be so far down the list as non essential. Microsoft, focus on the important tasks first before this one.

  • Adam Stone commented  ·   ·  Flag as inappropriate

    Managing domains with a third party creates so much unnecessary work. If Microsoft is trying not to spoil a helpful partnership with GoDaddy, can't they just buy them and get past this already?

  • Anonymous commented  ·   ·  Flag as inappropriate

    This is one of the services which Amazon's AWS does very well now in Route-53. If Azure could offer the same (if not better) experience that would be greatly received for sure.

    I would also have a side request in relation to the DNS management, if Azure could follow the lead given by some of the bigger DNS managers (such as UltraDNS) and implement Apex Alias (root level C-Name) that would be perfect!

  • John N commented  ·   ·  Flag as inappropriate

    I believe this option is very important. Imagine, managing domains and App services on separate billing, separate dashboards, separate monitoring, all opened on multiple browser tabs. That's a bit painful but I can carry on. But if Microsoft adopted this option as an azure service offering, that would be great.

    Also, I'm a bit confused about the "Azure DNS" and "Custom domains" section in the App Service. In the custom domains section we can purchase a domain name or add a domain name registered in a third party registrar. But if we can actually purchase a domain in azure, I think the "Buy domain" should be moved inside the Azure DNS, then all DNS options and configuration should be done inside Azure DNS to make it streamlined. If Azure DNS is only for High Availability purposes, then maybe we can just combine it. When we purchased a new domain in Azure DNS, it should be automatically configured for High availability and Hosted features, then it's up to the user if he wants to turn off this feature to lower the cost.

  • René Verhagen commented  ·   ·  Flag as inappropriate

    Absolutely, create this option rather sooner than later. Currently, we have to register domains with a separate company, which only acts as the registrar, and then perform all of the management of the domain in Azure. Having Microsoft act as the domain registrar and Azure as the management portal for the domain would absolutely be best.

    However, given the fact that this request as well as the response are as old as november 2013, I have the impression that we'd better give up hope about this. If Microsoft would have considered this, I believe by now this already could/would have been implemented...

    Any reply would be greatly appreciated, thanks!

    Regards, René

← Previous 1 3

Networking: DNS

Categories

Feedback and Knowledge Base

(thinking…)
Hosted by UserVoice