DNAME Record Alias

The DNAME record (Delegation Name) creates an alias for an entire subtree of the domain name space. While a CNAME record creates an alias for a single name, a DNAME redirects all names under a domain to another domain.

Look Up DNAME Records

Check DNAME records for any domain using our free DNS lookup tool.

Look Up DNAME Records →

What Is a DNAME Record?

A DNAME record substitutes one domain name for another at the DNS level. When a query matches a DNAME record, the queried name is rewritten by replacing the DNAME owner with the target.

Think of it as a "bulk redirect" — instead of creating individual CNAME records for every subdomain, a single DNAME record handles all of them automatically.

DNAME Record Format

Example DNAME Record

old.example.com.    3600    IN    DNAME    new.example.com.

All queries for anything.old.example.com will be rewritten to anything.new.example.com.

How DNAME Works

When a resolver queries for a name under a DNAME:

  1. Query: "What is the A record for api.old.example.com?"
  2. DNAME record found: old.example.com → new.example.com
  3. Name rewritten: api.old.example.com → api.new.example.com
  4. Resolver queries: "What is the A record for api.new.example.com?"
  5. Returns synthesized CNAME + final answer

DNAME vs CNAME

Aspect CNAME DNAME
Scope Single name Entire subtree
Example www → other.com old.* → new.*
Affects owner name Yes No (only subdomains)
Can coexist No other records Can have other records
Use case Simple alias Domain migration

Common DNAME Use Cases

1. Domain Migration

Redirect all subdomains from old domain to new domain:

old-company.com.    DNAME    new-company.com.

This redirects shop.old-company.com → shop.new-company.com, etc.

2. Reverse DNS Delegation

DNAME is commonly used in IPv6 reverse DNS:

8.b.d.0.1.0.0.2.ip6.arpa.    DNAME    ip6.example.com.

3. Organizational Restructuring

Redirect a department's subdomain to a new location:

engineering.old.example.com.    DNAME    engineering.new.example.com.

DNAME Restrictions

  • Does not affect the owner — DNAME at old.example.com doesn't affect old.example.com itself, only subdomains
  • Cannot be at zone apex — Like CNAME, DNAME can't coexist with SOA/NS at the root
  • One DNAME per name — Only one DNAME record can exist at a given name
  • Client support varies — Some older resolvers may not handle DNAME correctly

DNAME Best Practices

  • Use for migrations — DNAME is ideal for redirecting entire subdomains during domain changes.
  • Consider client compatibility — Some older clients may not support DNAME.
  • Plan for the owner name — Create a separate CNAME or A record for the DNAME owner if needed.
  • Test thoroughly — Verify DNAME works with your target services before going live.
  • Document the change — DNAME can be confusing; document its presence clearly.

Synthesized CNAMEs

When a resolver encounters a DNAME, it synthesizes a CNAME record for the queried name. The response includes both the DNAME and the synthesized CNAME: 

Query: api.old.example.com A

Answer:
old.example.com.      DNAME   new.example.com.
api.old.example.com.  CNAME   api.new.example.com.
api.new.example.com.  A       192.0.2.1

Troubleshooting DNAME

Common issues and solutions:

  • DNAME owner not redirecting — DNAME only affects names under it, not the owner itself. Add a CNAME or A record for the owner.
  • Old client not following DNAME — The client may not support DNAME. Use individual CNAMEs as fallback.
  • Loops — Ensure DNAME target doesn't point back to create circular references.
  • DNSSEC issues — DNAME requires proper DNSSEC handling; validate signing.

Check Your DNAME Records

Use our DNS Record Finder to look up DNAME records for any domain.

Look Up DNAME Records →

Related Record Types