Sorry to hear you’re having trouble. We’re working on enabling this for Support subscriptions. If you’re the user who purchased the Support subscription, please try downloading the invoice at https://account.windowsazure.com/subscriptions.
Any updates/news/guidance ... ?
An import of a 200MB bacbac from a storage account into a S3 tier db is taking > 2h.
This is simply unacceptable...
35 votes4 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
Thanks for the suggestion. We are tracking this on our backlog.
Some background: Azure DNS supports multiple name servers, which are dynamically assigned as zones are created. This allows us to let customers create zones without first proving that they own the domain name (since if we supported only a single name server set, we couldn’t allow just anyone to create a zone and thereby block the legitimate domain name owner). Domain proof-of-ownership checks are a significant hassle, so it’s important that we avoid them where possible.
Having said all that, I do understand that in some scenarios having a consistent set of name server names is desirable, and we are considering options for how we might support this in future.
We plan to move 350 domains from our self-hosted nameservers. How about allowing customers to use a single name server set after a manual trust establishment process?
We are thinking of enabling an easy way to download a dynamic VHD to reduce the download size, if that helps? Unfortunately, I don’t think VHD files compress that well.