What is our primary use case?
It's primarily used for managing domain names and ensuring proper resolution of IPs and domains. This is essential for setting up load balancers, traffic managers, and other network-related configurations.
What is most valuable?
Azure DNS is mainly focused on providing name resolution services. Its primary function is to ensure that domain names are correctly resolved to the corresponding IP addresses. As for the integration with other Azure services, it's tightly integrated like any other service within the Azure ecosystem.
What needs improvement?
There's always room for improvement in any product.
The reason I rate it highly is because within Azure, everything is managed through a single console called the Microsoft Azure management console. This console provides access to all the features and configurations, including DNS. You can easily browse through the menus, enable or disable features as needed, without having to deal with complex configurations. Additionally, Azure DNS is constantly stable, and each option in the console provides clear information about its impact when enabled or disabled. This makes it straightforward and simple for anyone to configure.
For how long have I used the solution?
I have been using Azure DNS for the past 5 years.
What do I think about the stability of the solution?
As for scalability, Azure DNS is indeed scalable, but there are limitations due to its nature as a specialized service. Currently, around two thousand users are utilizing DNS, and yes, there are plans to expand its usage further
What do I think about the scalability of the solution?
Azure DNS needs to be consistently stable because any failure can make our organization unreachable from outside. It's crucial for DNS to be stable 24/7, as even a momentary failure can disrupt accessibility. In terms of stability, I would rate it a solid eight out of ten. While it's stable, there's always room for improvement to ensure it remains reliable.
How are customer service and support?
We've had interactions with Microsoft, although not specifically related to DNS. Generally, we've discussed various matters with them. If any issues arise at the DNS level, we would likely reach out to Microsoft for assistance, as they are the service provider. However, personally, I haven't contacted Microsoft for DNS-related issues.
What was our ROI?
Azure DNS is designed to support a hundred percent reliability. If implemented correctly with the right design, it can ensure uninterrupted uptime, performance, and reliability. However, the actual reliability may vary depending on how it's built and deployed in different organizations. In our organization, we've implemented it to achieve a hundred percent reliability, but it's uncertain how others may configure it.
What's my experience with pricing, setup cost, and licensing?
In my opinion, DNS is inexpensive. The pricing depends on how you use it, but overall, it's quite affordable. It typically costs just a fesw cents, and Microsoft even offers ten thousand free hits per month.
What other advice do I have?
Overall, I'd recommend Azure DNS for anyone starting out, as it's an essential service used by everyone on a daily basis. I would rate Azure DNS a solid ten. It's crucial for DNS to be consistently online, as even a brief downtime can disrupt access to websites. Building DNS with the right level of redundancy and high availability ensures uninterrupted service. However, the reliability ultimately depends on how the product is built and the specific requirements of the developers. I would rate it high as well, maybe not a perfect ten, but at least a nine.
*Disclosure: I am a real user, and this review is based on my own experience and opinions.
