Introduce 'Vanity name servers'
We would like to see an introduction of delegations using name server names in our own zone (sometimes called 'vanity name servers').
Using 'vanity name servers' are important for consolidating our corporate brand.
Currently, the 'host' field of the SOA and the NS records at the zone apex are deliberately locked to discourage us from setting up delegations other than via the Azure DNS name server names.
We realise such delegations would break were we ever to change the Azure DNS name server IP ranges in future, which would obviously need to be resolved prior to the introduction of this.
Nevertheless, we feel it is an important feature that should be considered.
Good feedback. We’re tracking this as a backlog item, but please note it’s likely to be quite far out. Please keep your votes coming!
Really need this. Have multiple domains and different NS for the domains is a real pain to manage. Cannot use Azure DNS for this. Please make this happen.
Aaron Sadler commented
Any updates on this? Been a few years
Paul Baxter commented
Get's my vote!
Matt Richardson commented
What does "quite far out" mean? Is there hope for us on this?
Juan Pablo Apaza commented
I support this request, I believe it's something we need to move to Azure DNS.
We need this feature to provide and manage DNS service for our customers with our own domain name for NS records and delegations, like AWS does. :D
I second this need
Jack Evans commented
This is essentially preventing us from moving our DNS to Azure. Aside from the vanity aspects of this, when you have large numbers of domains across multiple registrars it's virtually impossible to get those domain owners to make the DNS server changes correctly. For example we tell our customers to use ns1. through ns6.fcbis.com when they register domains.