Azure DNS
Author: Ronald Fung
Creation Date: 17 May 2023
Next Modified Date: 17 May 2024
A. Introduction
Azure DNS is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.
You can’t use Azure DNS to buy a domain name. For an annual fee, you can buy a domain name by using App Service domains or a third-party domain name registrar. Your domains then can be hosted in Azure DNS for record management. For more information, see Delegate a domain to Azure DNS.
B. How is it used at Seagen
As a biopharma research company using Microsoft Azure, you can use Azure DNS to host your domain name system (DNS) domains in Azure. Here are some ways you can use Azure DNS:
Domain hosting: Azure DNS can help you to host your DNS domains in Azure, providing a reliable and scalable DNS service for your applications and services.
DNS management: Azure DNS provides a web-based management portal and a REST API that can help you to manage your DNS domains and records. You can create, update, and delete DNS records, and manage TTLs and zone transfers.
Integration with Azure services: Azure DNS can integrate with other Azure services such as Azure Traffic Manager and Azure Load Balancer. This can help you to manage traffic routing and load balancing for your applications and services.
Global availability: Azure DNS provides global availability and low latency for your DNS domains, with DNS servers located in multiple Azure regions around the world.
Security and compliance: Azure DNS provides security features such as DNSSEC (Domain Name System Security Extensions) and access control. It also complies with regulatory requirements such as GDPR and HIPAA.
Cost-effective: Azure DNS is a cost-effective solution for hosting and managing your DNS domains in Azure, with pay-as-you-go pricing and no upfront costs.
Overall, Azure DNS can help your biopharma research company to host and manage your DNS domains in Azure, with fast and reliable DNS resolution, integration with Azure services, global availability, security and compliance, and cost-effectiveness. With Azure DNS, you can ensure the availability and performance of your applications and services, simplify DNS management, and reduce costs.
C. Features
Common DevTest Labs scenarios
Common DevTest Labs scenarios include development VMs, test environments, and classroom or training labs. DevTest Labs promotes efficiency, consistency, and cost control by keeping all resource usage within the lab context.
Custom VM bases, artifacts, and templates
The following features are included with Azure DNS.
Reliability and performance
DNS domains in Azure DNS are hosted on Azure’s global network of DNS name servers. Azure DNS uses anycast networking. Each DNS query is answered by the closest available DNS server to provide fast performance and high availability for your domain.
Security
Azure DNS is based on Azure Resource Manager, which provides features such as:
Azure role-based access control (Azure RBAC) to control who has access to specific actions for your organization.
Activity logs to monitor how a user in your organization modified a resource or to find an error when troubleshooting.
Resource locking to lock a subscription, resource group, or resource. Locking prevents other users in your organization from accidentally deleting or modifying critical resources.
For more information, see How to protect DNS zones and records.
DNSSEC
Azure DNS does not currently support DNSSEC. In most cases, you can reduce the need for DNSSEC by consistently using HTTPS/TLS in your applications. If DNSSEC is a critical requirement for your DNS zones, you can host these zones with third-party DNS hosting providers.
Ease of use
Azure DNS can manage DNS records for your Azure services and provide DNS for your external resources as well. Azure DNS is integrated in the Azure portal and uses the same credentials, support contract, and billing as your other Azure services.
DNS billing is based on the number of DNS zones hosted in Azure and on the number of DNS queries received. To learn more about pricing, see Azure DNS pricing.
Your domains and records can be managed by using the Azure portal, Azure PowerShell cmdlets, and the cross-platform Azure CLI. Applications that require automated DNS management can integrate with the service by using the REST API and SDKs.
Customizable virtual networks with private domains
Azure DNS also supports private DNS domains. This feature allows you to use your own custom domain names in your private virtual networks rather than the Azure-provided names available today.
For more information, see Use Azure DNS for private domains.
Alias records
Azure DNS supports alias record sets. You can use an alias record set to refer to an Azure resource, such as an Azure public IP address, an Azure Traffic Manager profile, or an Azure Content Delivery Network (CDN) endpoint. If the IP address of the underlying resource changes, the alias record set seamlessly updates itself during DNS resolution. The alias record set points to the service instance, and the service instance is associated with an IP address.
Also, you can now point your apex or naked domain to a Traffic Manager profile or CDN endpoint using an alias record. An example is contoso.com.
For more information, see Overview of Azure DNS alias records.
D. Where Implemented
E. How it is tested
Testing Azure DNS involves ensuring that the service is functioning correctly and securely, and meeting the needs of all stakeholders involved in the project. Here are some steps to follow to test Azure DNS:
Define the scope and requirements: Define the scope of the project and the requirements of all stakeholders involved in the project. This will help ensure that Azure DNS is designed to meet the needs of all stakeholders.
Develop test cases: Develop test cases that cover all aspects of Azure DNS functionality, including creating and managing DNS zones, configuring DNS records, and resolving DNS queries. The test cases should be designed to meet the needs of the organization, including scalability and resilience.
Conduct unit testing: Test the individual components of Azure DNS to ensure that they are functioning correctly. This may involve using tools like PowerShell or Azure CLI for automated testing.
Conduct integration testing: Test Azure DNS in an integrated environment to ensure that it works correctly with other systems and applications. This may involve testing Azure DNS with different operating systems, browsers, and devices.
Conduct user acceptance testing: Test Azure DNS with end-users to ensure that it meets their needs and is easy to use. This may involve conducting surveys, interviews, or focus groups to gather feedback from users.
Automate testing: Automate testing of Azure DNS to ensure that it is functioning correctly and meeting the needs of all stakeholders. This may involve using tools like Azure DevOps Pipelines to set up automated testing pipelines.
Monitor performance: Monitor the performance of Azure DNS in production to ensure that it is meeting the needs of all stakeholders. This may involve setting up monitoring tools, such as Azure Monitor, to track usage and identify performance issues.
Address issues: Address any issues that are identified during testing and make necessary changes to ensure that Azure DNS is functioning correctly and meeting the needs of all stakeholders.
By following these steps, you can ensure that Azure DNS is tested thoroughly and meets the needs of all stakeholders involved in the project. This can help improve the quality of Azure DNS and ensure that it functions correctly in a production environment.
F. 2023 Roadmap
????
G. 2024 Roadmap
????
H. Known Issues
There are several known issues that can impact Azure DNS. Here are some of the most common issues to be aware of:
Resource limitations: Azure DNS has resource limitations that can impact the number of DNS zones and records that can be used. It is important to ensure that the service is properly sized to meet the needs of the organization.
Performance issues: If the service is not properly sized, it can impact performance and availability, causing issues with the speed and reliability of Azure DNS.
Security issues: Security is a critical concern when it comes to Azure DNS. It is important to ensure that Azure DNS is secured and that access to the solution is restricted to authorized personnel.
Compatibility issues: Azure DNS may not be compatible with all platforms, devices, or languages. It is important to ensure that Azure DNS is compatible with the organization’s existing infrastructure before implementation.
Scalability issues: Scalability issues can arise when scaling up or down the service. It is important to ensure that the service can scale to meet the needs of the organization.
Integration issues: Integration issues can arise when integrating Azure DNS with other systems and applications. It is important to ensure that Azure DNS is designed to work seamlessly with other systems and applications to avoid integration issues.
Testing issues: Testing issues can arise when testing Azure DNS. It is important to ensure that testing is carried out thoroughly and that all aspects of Azure DNS functionality are tested.
Licensing issues: Licensing issues can arise when using Azure DNS. It is important to ensure that the appropriate licensing is in place to avoid any legal issues.
Overall, Azure DNS requires careful planning and management to ensure that it is functioning correctly and meeting the needs of all stakeholders involved in the project. By being aware of these known issues and taking steps to address them, you can improve the quality of Azure DNS and ensure the success of your project.
[x] Reviewed by Enterprise Architecture
[x] Reviewed by Application Development
[x] Reviewed by Data Architecture