Azure DNS Reviews

We are working at a DSK and use Azure DevOps as we work in Azure DevOps infrastructure engineering. So we use various Azure services. We have migrated Azure services from on-premises to Azure Cloud and multiple services like microservices or application improvements or applications replacing Azure administrators.

The process of creating a virtual mission could be improved.

We have been using this solution for the past four years. It is deployed on-premises. 

It is a stable solution. 

It is a scalable solution. 10 to 15 people are using this solution.

The setup was not difficult.

I rate this solution a seven out of ten because it is a hosting service. However, I would recommend this solution to others.

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.

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.

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.

I have been using Azure DNS for the past 5 years.

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

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.

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. 

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.

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.

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.

We use it to connect to our networks from the AD side and resolve host names to IP addresses, identify machines available as per the main domain, and create CNAME records and alias lists in Azure AD.

I've found all of the features to be valuable because we are using it extensively. 

Moreover, Microsoft regularly notifies us about upcoming changes. They have a cycle of introducing features in preview mode before a global release, along with a specific timeline. This helps us stay well-informed.

I would like to see more integration with other platforms, improved stability, enhanced security, and better pricing because there is always room for improvement. 

We've been utilizing Azure DNS for approximately eight years since its inception.

It is a stable solution. 

It's highly scalable and provides very good features from Microsoft. We are satisfied with it.

The support is always good. 

The setup is relatively straightforward. The solution is deployed both on-prem and cloud. 

To deploy it, all you need is a domain name and the necessary preparations. Once you have that, you can begin creating DNS records.

We are using most of the features offered by Azure. We have multiple tools wrapped around it. We have a combination of tools within the organization, and we are content with the setup we have.

I would definitely recommend using the solution. It is a good tool. 

Overall, I would rate the solution an eight out of ten. It provides a wide array of features required from a technical standpoint. It offers a variety of capabilities, and they can confidently adopt it. Most of the essentials are readily available in Azure DNS.

The DNS (Domain Name System) is a system used to provide domain names for virtual machines on the Azure cloud. Both third-party DNS and Microsoft DNS are options for users of Azure. Microsoft DNS is an inbuilt offering from Microsoft and can be used by those with workloads deployed on Azure. Azure DNS is primarily used for domain name resolution for virtual machines on the cloud.

One of the key benefits of Azure DNS is its integration with other Azure services. As it is a solution developed by Microsoft, it is easy to integrate with other Azure offerings. Azure DNS also includes Defender for DNS, a feature that protects against anomalies and threats on the DNS. This added security is provided directly by Microsoft. The integration and security features of Azure DNS make it a valuable option for users of the Azure cloud platform.

Azure DNS does provide enhanced support for applications and includes several security features to protect against threats. One of the security features it offers is the ability to detect and prevent dangling DNS records, which can be used in cyber attacks. Dangling DNS records occur when a website owner creates a domain name but forgets to remove the CNAME record, leaving the domain vulnerable to takeover by malicious actors. Azure DNS includes security measures to identify and prevent such threats, helping to keep your DNS infrastructure secure. However, if Microsoft could add more security capabilities to the DNS, that would be great to detect and identify anomalies that are happening to prevent cyber threats.

I have been using Azure DNS for approximately five years.

The solution is 100 percent stable. The stability is managed by Microsoft.

Azure DNS is a scalable solution. The scaling is done by Microsoft, we do not have to worry about it.

Using Azure DNS does not require extensive technical expertise. If support is needed, you can simply raise a ticket with Microsoft and one of their product engineers will assist you. This means that you do not need to invest in external or third-party technical support, making it a convenient and cost-effective solution.

The level of support you receive from Microsoft when using Azure DNS will depend on the support plan you have with them. If you are a larger enterprise with a Premier support plan, you will typically receive more support and have a shorter response time from Microsoft. For smaller companies, the support plans and response times may be different. It is important to carefully consider your support needs and choose a plan that meets the requirements of your company.

We have used other in-house solutions which are vNEXT-based DNS or Windows-based DNS. These were systems we are fully in control of and do the deployment but Azure DNS is a complete Microsoft cloud offering. It is the most advanced version of DNS we can have.

The initial setup of the solution is simple because it is on the cloud. It only takes a few clicks of the mouse. For example, for a volume of a thousand virtual machines, it takes one day to implement.

To implement Azure DNS, the following steps can be taken:

1. Deploy a virtual machine on a VNET in Azure.
2. On the VNET blade, select Microsoft DNS as the DNS provider. Alternatively, you can choose to use a third-party DNS provider by selecting the corresponding radio button.
3. Click the radio button to confirm your choice of DNS provider.

No additional configuration is required, as Azure DNS is an in-house product from Microsoft and is already integrated with other Azure services. You can simply select it as the DNS provider for your virtual machine and it will be ready to use.

Using Azure DNS can provide a good return on investment for your company. As a fully managed offering, it does not require any hardware investment or maintenance, so there is no upfront capital expenditure (CapEx) costs. You can pay for Azure DNS on a pay-as-you-go basis, which means that your operating expenditure (OpEx) costs will be based on actual usage. This can be more cost-effective than managing and scaling your own DNS infrastructure, as you do not need to invest in hardware or hire specialized staff to maintain it. Using a cloud-based DNS solution, such as Azure DNS can provide a high return on investment due to its low upfront costs and flexibility.

Azure DNS is generally not priced separately. It is included as part of the overall Azure licensing and is typically charged based on usage. This means that you only pay for the resources you use, such as the volume of traffic on your DNS. There is no specific pricing for Azure DNS assets, as it is part of the overall Azure pricing model. You can choose a pay-as-you-go plan, which charges based on actual usage, or a subscription plan, which allows you to pay a fixed rate for a set amount of resources.

I rate Azure DNS an eight out of ten.

We use the solution to manage domains.

It is a robust solution.

They should include more integration with other platforms.

We have been using the solution for one year.

It is a stable solution. I rate its stability as a ten.

Our organization has five solution users and plans to increase usage. It is very scalable.

The solution's technical support team is responsive.

The solution's initial setup process is easy and takes a few minutes to complete. The technical teams for deployment consist of administrators, system engineers, managers, and developers.

We take help from a third-party vendor to implement the solution.

The solution's price is reasonable. We purchase its yearly license.

I rate the solution as a nine.

We use the solution to spare some names and domains from the host to another destination.

There are issues with the cloud systems. The Bank of Egypt restricts paying anything through the Internet in dollars. I set up an Active Directory on Azure and joined computers to it. This involved creating a domain controller on Azure and then using DNS to ensure smooth operation over the DC, allowing the controller to translate domain names into IP addresses.

I have been using Azure DNS for ten months.

Ten users are using this solution.

We contact customer support twice a week.

I faced issues with Microsoft, so I migrated my operating system from Microsoft to another platform, such as Linux.

Azure DNS is a compelling choice, where data protection is paramount across cloud platforms. While cloud systems offer significant advantages for small businesses, enterprises may find greater value in comprehensive admin integrations and robust DNS solutions to safeguard their data and operations. In this context, investing in a cloud platform like Azure seems to be the future for small and medium-sized enterprises. On the other hand, on-premises projects or data centers might become obsolete for specific industries due to their limitations in scalability and security compared to cloud solutions.

Overall, I rate the solution a seven out of ten.

I am using Azure to host the DNS records.

I like the feature where I can add multiple DNS records for the same subdomain.

Domain registration is one of the problems. We need to go to application services or web apps to purchase the domain instead. If that were to be equivalent to AWS's Route 53 that would be good. But, it is not as flexible as that.

Also, there is no clear information on the functionality of Azure DNS or the features of Azure DNS. For example, there is no information provided on the DDI feature and whether it is available or not.

I have been using this solution for more than two years.

It is stable. We did not have an issue.

It is an easily scalable solution. I would the scalability a nine out of ten.

The support team is good. They support well and we don’t have to implement anything. Since we have a premium plan, the response time is probably less than one hour.

The initial setup is straightforward.

I deployed the hybrid version because the domains are posted somewhere, and I am using DNS on Azure.

I did the installation by myself as it is easy. 

The price is low and it's a reasonable price for that product.

I recommend the product to the users.

We use the solution to host IP addresses, sites like microsites. 

I would like to see more security features and protection. 

I have been working with the product for four years. 

The solution is stable. 

The product is scalable. 

I have used tech support only minimally. 

The solution's setup is okay. 

Consultants helped us with the solution's setup. 

I would rate the product an eight out of ten.