Forum Discussion
Azure DNS zone security
nadsurf93, when you provision a DNS Zone in Azure, you are simply using a PaaS service that will allow you to delegate DNS resolution for a domain you own. An Azure DNS Zone by itself is useless until you configure your domain registrar to use Azure DNS name servers for your domain. That's why you don't have to prove ownership to Azure - you can only configure your registrar settings to use Azure name servers if you own the domain, of course.
For each DNS Zone, Azure will provide you with 4 name server addresses. If you have multiple Azure DNS Zones with the same name, then their name servers must be different, because this will be the glue between Azure DNS and your registrar configuration.
More details on Azure DNS delegation here.
Microsoftnadsurf93, when you provision a DNS Zone in Azure, you are simply using a PaaS service that will allow you to delegate DNS resolution for a domain you own. An Azure DNS Zone by itself is useless until you configure your domain registrar to use Azure DNS name servers for your domain. That's why you don't have to prove ownership to Azure - you can only configure your registrar settings to use Azure name servers if you own the domain, of course.
For each DNS Zone, Azure will provide you with 4 name server addresses. If you have multiple Azure DNS Zones with the same name, then their name servers must be different, because this will be the glue between Azure DNS and your registrar configuration.
More details on Azure DNS delegation here.
- Dear hspinto,
I suspected that it was the case (since when I created the zone on the new tenant it gave me a different set of name records).
And I was able to change the name servers on my registrar account so that it would point to the "new" name servers.
I just wanted to lay this worry to rest (DNS is critical after all).
In any case, many thanks for having provided this information.
