Best in class DNS Solution
January 13, 2023
Best in class DNS Solution
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Azure DNS
So basically, all our infrastructure is on Azure, so it makes sense to use the Native DNS (Azure DNS) for all our domain resolution services. We use its both public and private variants. Public for our public-facing websites and private for all our internal resources such as VMs and private links/Endpoints.
- The Azure Private DNS has an option for automatic mapping which creates a DNS record automatically for all the resources in a particular Vnet, and adds new DNS entries for whenever a new resource is created.
- The DNS entries can be shared between different VNets automatically and there is no need for manually populating it or syncing it with different networks.
- The mapping or records is very easy as the target/source/backend is automatically populated and there is no need to keep those IP addresses handy instead you can map them using their name.
- I honestly haven't faced a single issue while using Azure DNS as a whole.
- I did face some issues while using it with Azure Front door but it was because of an automatic population of records by the front door and nothing that Azure DNS could have done in that case.
- Automatic Integration with VNets
- Automatic population of new resources and their record propagation
- No need for managing a separate DNS server.
- No need for managing/ running a separate DNS Server reduces costs.
- Lower chances of downtime.
- Ease of use and maintenance for Admin team.
As we have all our infrastructure on Azure it was much more feasible for us to use Azure DNS.
Do you think Azure DNS delivers good value for the price?
Yes
Are you happy with Azure DNS's feature set?
Yes
Did Azure DNS live up to sales and marketing promises?
Yes
Did implementation of Azure DNS go as expected?
Yes
Would you buy Azure DNS again?
Yes