To get to the meaning of DNS Delegation, first, let’s see two things. One is the Domain Name System itself, and the second is the definition of delegation. To delegate, it means to give the right to manage, the control of some resources or tasks to another.
DNS Zones and Domains
The DNS is a hierarchy structure of domains. It starts from the root domain “.”. Underneath it, there are the TLD domains like “com”, “org”, “net” and so on. Then it is time for the domains of the second level like “co.uk” and so on. All of the domains are hosted using different DNS zones, which are globally distributed and hosted by DNS servers in different international locations.
What is DNS Delegation?
DNS Delegation, also called DNS Zone Delegation, is a process of assigning authority over a domain or subdomain to different DNS servers to keep records updated. When the Authoritative DNS server to which the zone is delegated responds to DNS requests, it recursively resolves the CNAME target or responds with a referral. By delegating responsibility over a subdomain to another DNS server, an organization can receive more control over the enabling and disabling services, such as mail exchange, hosted on the subdomain.
When do you need DNS Delegation?
The DNS gives you the option to separate the namespace into different DNS zones. You can save them, copy them or distribute them to other DNS servers. There are few reasons to do it:
- You would like to load balance by dividing one large zone into more, smaller zones. This will increase the DNS resolution and add extra security.
- You desire to delegate management of part of your DNS namespace to another location or department in your organization.
- Use the DNS Delegation for adding various subdomains. Use them for different purposes.
- Delegate control of part of your DNS namespace to another location.
- You can restructure your namespace and make other DNS servers responsible for a part of the whole information.
When you create new DNS zone, you must have delegation records in other zones that point toward the authoritative DNS servers for the new one.
The resource record information of the new DNS zone will be stored in a DNS server, which will be the primary master for that zone. You can improve the security and duplicate the zone information to another DNS server, such as Secondary DNS. It will serve as a backup DNS and will give you additional protection.
How do you delegate a subdomain?
Delegating authority over a subdomain to another organization or DNS server is a simple process. All you need to do is add NS records for the subdomain into the parent domain, pointing at the delegated server. This means that the trusted server will handle all DNS requests related to the subdomain. However, it is essential to be careful when delegating a subdomain, as any problems with the server or domain management will reflect badly on you. Therefore, it is recommended to use the “dig +norec” command on all the servers to check that the delegated server is authoritative for the subdomain before delegating it.
- Provides an additional layer of security as delegated servers can be set up to work as a failover in the event of a system failure on the root server
- Delegated servers can employ more secure protocols than the root server, such as DNSSEC (Domain Name System Security Extensions)
- Allows organizations to create multiple backups, ensuring data and resources are fully protected in the event of an attack
- Reduces the attack surface by compartmentalizing the authoritative server from its clients, preventing DNS attacks
DNS Delegation example
DNS zone delegation is a process that allows organizations and companies to delegate authority over a portion of their DNS namespace to another entity. This means an external party can manage a part of a domain’s DNS settings, such as adding or removing A records or CNAME records.
There are many examples where companies delegate part of their DNS space. Such as examples are universities that have delegated a portion of their namespace for managing student email accounts. Or businesses that have delegated their Domain Name System to a third-party service provider, like ClouDNS, to provide better speed, security, and reliability for their website.
Here are some examples of what we explained above:
- Subdomain delegation – assigning a DNS server for a specific subdomain such as ‘email.university.com’ to be managed separately from the root domain ‘university.com’.
- Domain alias delegation – For domains in different TLDs (Top Level Domains) such as ‘example.com’ and ‘example.net’, delegating part of the DNS management to another server, allowing the same DNS records to be shared across both domains.
Glue records: The key to effective DNS Delegation
In the context of DNS Delegation, Glue records play an indispensable role by linking the parent domain with its subdomains. Essentially, these records function by providing the required A and AAAA records that establish a connection between the primary domain and its delegated counterparts. Glue records are particularly crucial for resolving what are known as circular dependencies, which arise between domain names and their associated nameservers.
Suggested article: What DNS Branding is?
To illustrate, let’s consider an example: a main domain named example.net is delegating a subdomain, say, blog.example.net, to dedicated nameservers – ns1.blog.example.net and ns2.blog.example.net. In this scenario, because these nameservers are under the subdomain they are assigned to manage, Glue records are essential. They help in pinpointing the IP addresses of these nameservers. Absent these Glue records, the DNS would find itself in an endless resolution cycle, unable to properly locate the nameservers. Therefore, the parent domain, example.org in this case, must include not only the NS records that indicate delegation but also the A (or AAAA) records that effectively link the nameserver names to their IP addresses, ensuring a smooth and uninterrupted DNS resolution process.
What is reverse DNS zone delegation?
Reverse DNS zone delegation is a process that allows organizations to delegate responsibility over a PTR (Pointer) record to a different zone within their domain name space. It is a two-step process where the organization’s name servers have first delegated the responsibility to handle the DNS records related to its domain names, then the reverse DNS zone.
Reverse DNS Delegation enables organizations to provide faster resolution for DNS requests. Furthermore, it is usually used for security and reliability purposes and for instituting adequate access control policies. By employing rDNS Delegation, organizations can have more control over how their domain and subdomains are accessed and managed.
Lame delegation occurs in DNS when a nameserver is incorrectly configured or fails to respond authoritatively for a domain it’s listed to serve. This often happens when the NS records in the parent domain point to a server that is not configured for the specified subdomain, resulting in failed or improper DNS queries.
For instance, consider a domain, example.net, that delegates a subdomain, blog.example.net, to a set of nameservers. If one of these nameservers, say ns1.blog.example.net, is not correctly configured to resolve queries for blog.example.net, or if it’s completely unresponsive, this results in lame delegation. Clients trying to access blog.example.net might experience delays or inability to reach the site, as their DNS queries partially fail due to the non-responsive or misconfigured server.
To prevent lame delegation, it is crucial for domain administrators to regularly verify that all listed nameservers are correctly configured and responsive for all the domains and subdomains they are intended to serve. This includes ensuring that any changes in the DNS configuration are accurately reflected across all relevant nameservers. Regular monitoring and auditing of DNS settings are essential to identify and rectify any instances of lame delegation promptly, thereby maintaining the integrity and reliability of the DNS system.
DNS Delegation will significantly increase the performance of your DNS network. Thanks to this feature, the whole DNS is so easily scalable. It will reduce the load, increase the speed and redundancy. It is used for almost all subdomains. Knowing how to manage your DNS will increase the performance greatly.
Hi, I’m Martin Pramatarov. I have two degrees, a Technician of Computer Networks and an MBA (Master of Business Administration). My passion is storytelling, but I can’t hide my nerdish side too. I never forgot my interest in the Hi-tech world. I have 10 years and thousands of articles written about DNS, cloud services, hosting, domain names, cryptocurrencies, hardware, software, AI, and everything in between. I have seen the Digital revolution, the Big migration to the cloud, and I am eager to write about all the exciting new tech trends in the following years. AI and Big Data are here already, and they will completely change the world!
I hope you enjoy my articles and the excellent services of ClouDNS!