Black Friday promo up to -50% Time left:

What is a DNAME Record? Redirect Subdomains Easy

The DNAME record provides redirection from a part of the DNS name tree to another part of the DNS name tree. The short acronym DNAME stands for "Delegation Name" and is a lesser-known yet highly useful resource record within the DNS infrastructure. Unlike traditional records such as A (Address) or CNAME (Canonical Name), which resolve individual hostnames, the DNAME record operates at a broader scale, simplifying domain name redirection and aliasing.

The DNAME record has the following look in your ClouDNS Control Panel:

Host Type Points to TTL
www.domain.net DNAME hostname.com 1 Hour

Why use a DNAME record?

The DNAME record should be used when you want to redirect an entire branch of the DNS hierarchy to a new domain name. It simplifies DNS management by redirecting multiple subdomains with just a single record. It is especially valuable during domain name changes and regional redirection. With DNAME records, administrators can efficiently manage large-scale domain infrastructures, delegate subdomains, and ensure smooth DNS resolution across the network. However, careful consideration and testing are essential to prevent potential issues.

How to create a DNS DNAME record?

Log in to your ClouDNS account, enter your DNS zone management page, and click on the Add new record button. For Type choose "DNAME" and type as follow:

  • Type: DNAME
  • TTL: 1 hour
  • Host: www
  • Points to: hostname.com

*This hostname is used as an example.

How to check it?

You can quickly check the DNAME record for a domain name by using one of the following commands based on our OS (Operating System):

If you are a Windows user, you can open the Command Prompt and check your DNAME records via Nslookup. Here is an example:

$ nslookup -q=DNAME example.com

If you are a Linux/macOS user, you can open the Terminal and check your DNAME record via DIG. Here is an example:

$ dig example.com DNAME

In case you prefer to use an online tool, you can check your DNAME record with the ClouDNS Free DNS tool.

DNAME record vs CNAME record

The DNAME and CNAME records both cause a lookup to (potentially) return data corresponding to a domain name different from the queried domain name. The difference between the two resource records is that the CNAME directs the lookup of data at its owner to another single name, whereas a DNAME directs lookups for data at descendants of its owner's name to corresponding names under a different (single) node of the tree.

How to start managing DNAME records for your domain name?

  1. Create a free account from, here - free forever
  2. Verify your e-mail address
  3. Log into your control panel
  4. Create a new Master DNS from the [add new] button - check a tutorial, here
  5. Add the DNAME records you need, as it is described in this article.

Support of DNAME records

ClouDNS provides full support for DNAME records for all our DNS services, including the listed below. Just write to our technical support, if you need any assistance with your DNAME records configuration. Our Technical Support team is online for you 24/7 via live chat and tickets.

FAQ

Question: Are there any potential issues with using DNAME records?

Answer: DNAME records are powerful but require careful consideration and testing. Compatibility with DNS servers should be verified before implementation. Improper use can lead to cyclic redirection loops, DNS resolution problems, and performance issues.

Question: What impact do DNAME records have on DNS resolution?

Answer: Implementing DNAME records may introduce a slight delay in DNS resolution due to the redirection process. However, the impact is usually minimal.

Question: Should I use DNAME records for small-scale domain management?

Answer: Carefully evaluate the use cases for DNAME records. Overusing them for small-scale domain management might complicate DNS resolution and lead to inefficiencies.


Last modified: 2024-09-24
Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more