Microsoft offers Azure DNS, a managed network of name servers supplying availability, support for migration, and DNS security.
$0.10
per zone/per month
Azure Traffic Manager
Score 9.7 out of 10
N/A
Microsoft's Azure Traffic Manager operates at the DNS layer to quickly and efficiently direct incoming DNS requests based on the routing method of your choice.
Using Azure DNS, you can easily and quickly deploy and manage your domain DNS. It's been an excellent introduction to our web services requirements. It offers all services on a single platform and integrates with other applications. It not only offers DNS services for websites but also for your applications.
Azure Traffic Manager is a great product, if you have multiple sites hosting similar services (Primary and DR), and you want to ensure that users are directed to the DR in case of a primary datacenter failure, [Azure] Traffic Manager does this very nicely. If you have a service hosted across multiple regions/datacenters and you want to balance the inbound load between the regions, [Azure] Traffic Manager does this very well, of course such scenario would require a database replication or something like Cosmos-DB in the backend [Azure Traffic Manager] is also well suited for inbound traffic with multiple IPs, you can fail-over traffic from one inbound IP to another based on its availability, or if you have multiple internet connections that you want to balance the load across, it does this pretty nicely too.
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.
Traffic View is a great feature, but doesn't work very well, sometimes it gets stuck and stops loading traffic view data
Automatic probing for endpoints sometimes gets stuck too, I would recommend a technique to test the endpoint in real time from Azure Portal
Traffic View heatmap is buggy and doesn't point correctly to locations
Traffic View portal doesn't show source countries (Shows coordinates) it would be much more helpful to have coordinates auto-translated to geolocations/countries
The implementation process was fairly easy, quick, and straightforward compared to other estimated timelines from competitors. The price is fair for the service, while the customer success team and engineers know what they are doing, making the entire process smooth and comfortable. Also, they are a big and known brand, which makes us more at ease with our choice
Amazon Route 53 Traffic Flow does what [Azure] Traffic Manager does, however, in Azure Configuration is separated between Azure DNS Zones (For DNS Zone Management) and [Azure] Traffic Manager for DNS Traffic Management and Load Balancing, Route 53 in a unified product for DNS Traffic Management using Traffic Flow and DNS Zone Management. Route 53 does a great job, however, we found it to be a little bit more complex to setup than [Azure] Traffic Manager, Setting up traffic manager is pretty easy even for the first time, and getting the best out of it is relatively simple.
