Custom NS servers for Web hosts

Question

Hello,

We are a small web host that want to use Azure DNS for our clients. Currently we have our own NS servers that everyone points their domains to:

ns1.ourhostingplatform.com
ns2.ourhostingplatform.com
ns3.ourhostingplatform.com
ns4.ourhostingplatform.com

We have the hosting panel connected to AzureDNS and it works great (using Plesk Onyx), creates records seamlessly. However each domain that's added to the hosting panel which gets added to AzureDNS has their own set of NS servers assigned:

Domain1 would get:

ns1-37.azure-dns.com.
ns2-37.azure-dns.net.
ns3-37.azure-dns.org.
ns4-37.azure-dns.info.

Domain2 would get:

ns1-32.azure-dns.com.
ns2-32.azure-dns.net.
ns3-32.azure-dns.org.
ns4-32.azure-dns.info.

This will make it very much a pain getting all of our clients onto our servers if every record we create gets a different DNS server.
Is there a way to set custom records for those servers?
Is there a way to set any domains created under our AzureDNS to go to the same DNS servers? (ie: the ns1-4.ourhostingplatform.com)?

Thanks!

Answer 1

@Josh Henry

Thank you for reaching out.

I understand you are a web host using Azure DNS for your clients, but each domain added to the hosting panel gets assigned a different set of NS servers. You want to know if there is a way to set custom records for those servers or if there is a way to set all domains created under your Azure DNS to go to the same DNS servers.

As documented here NS record set contains the names of the Azure DNS name servers assigned to the zone. You can add more name servers to this NS record set, to support cohosting domains with more than one DNS provider. You can also modify the TTL and metadata for this record set. However, removing or modifying the prepopulated Azure DNS name servers isn't allowed. These NS records are generated at random.

This restriction only applies to the NS record set at the zone apex. Other NS record sets in your zone (as used to delegate child zones) can be created, modified, and deleted without constraint.

So, modifying for example ns1-37.azure-dns.com to ns1-4.ourhostingplatform.com is not allowed for zone apex.

Although if it helps if you wish to pin the Name Server to same set of Name Servers for example ns1-37.azure-dns.com for all the DNS zones in a resource group then you will need to create a support ticket with us as a support engineer will review your set-up and based on findings and conditions create a formal request internally to pin the name servers.

If you have a support plan you can file a support ticket. If you do not have a support plan, please let me know. I will help you in this regard.

Hope this helps! Please let me know if you have any additional questions. Thank you!