Using DNS Zone Editor in DirectAdmin

DNS records determine where your domain points. In this guide, we explain how to manage DNS records in DirectAdmin.

What is DNS?

DNS (Domain Name System) translates domain names to IP addresses. DNS records tell where your website, email, and other services are located.

Why manage DNS records?

You change DNS records when you:

• Move your website to another server
• Route email through an external service (for example Google Workspace or Microsoft 365)
• Point a subdomain to another server
• Need to verify ownership of your domain

Opening DNS Zone Editor

1. Log in to DirectAdmin
2. Go to DNS Zone Editor or DNS Management
3. Select your domain (if you have multiple)
4. You'll see all DNS records for this domain

Record types explained

Every record also has a TTL: the number of seconds other servers may cache the record. The DirectAdmin default is usually fine.

Creating an A Record

To point a (sub)domain to an IP:

1. Click Add Record
2. Type: A
3. Name: the name (e.g., blog for blog.example.com, or @ for example.com)
4. Value: the IP address (e.g., 123.45.67.89)
5. Click Add

Creating a CNAME Record

To create an alias:

1. Click Add Record
2. Type: CNAME
3. Name: the alias (e.g., www)
4. Value: the target domain with period (e.g., example.com.)
5. Click Add

MX Record for email

To route email:

1. Click Add Record
2. Type: MX
3. Name: @ or empty for main domain
4. Value: mail server (e.g., mail.example.com.)
5. Priority: 10 (lower = higher priority)
6. Click Add

TXT Record (SPF, verification)

For SPF, DKIM, or domain verification:

1. Click Add Record
2. Type: TXT
3. Name: @ for main domain
4. Value: the TXT value (e.g., v=spf1 a mx ~all)
5. Click Add

Editing records

1. Find the record in the list
2. Click Edit or the pencil icon
3. Change the value
4. Click Save

Deleting records

1. Find the record
2. Click Delete or the trash icon
3. Confirm the action

Note: Wrong changes can make your website or email unreachable. Do not delete records if you are not sure what they are for.

DNS propagation

After changes, it takes up to 24-48 hours for DNS to update worldwide. Check with:

• whatsmydns.net
• dnschecker.org

Common configurations

Website on external hosting

A     @     123.45.67.89
CNAME www   example.com.

Email via Google Workspace

MX    @     smtp.google.com.        (priority 1)
TXT   @     v=spf1 include:_spf.google.com ~all

Still using the older set of five Google MX records (ASPMX.L.GOOGLE.COM and the ALT servers)? That set keeps working.

Subdomain to another server

A     blog  98.76.54.32

DNS troubleshooting

Changes not visible

• Locally you often see a change within 1 to 2 hours, worldwide it can take up to 48 hours
• Clear your local DNS cache, for example with ipconfig /flushdns on Windows

Website unreachable after a change

• Check that the A record points to the correct IP address
• Check that the new server is set up for your domain

Email not working

• Check your MX records and their priorities
• Check your SPF and DKIM records
• Test with an online MX lookup, for example at mxtoolbox.com

Tips

1. Make a backup: Note existing records before changing
2. Test first: Check DNS propagation
3. Period after CNAME/MX: Don't forget the trailing period
4. Low TTL: Lower the TTL to for example 300 seconds a day before a planned change, so the new value is active everywhere sooner
5. Test with tools: Check records with dig, nslookup or an online DNS checker

Need help?

We're here for you! Running into issues or have questions? Our support team is happy to help you personally. Drop us a message through the ticket system - we usually respond within a few hours and love helping you find the best solution.