Understanding DNS Zones in DirectAdmin
DNS zone management forms the backbone of domain hosting. Your DirectAdmin control panel provides comprehensive tools to configure DNS records directly from your hosting account. Unlike basic domain pointing, zone management gives you granular control over how visitors and email reach your sites.
DirectAdmin stores DNS zones in BIND format. Each domain gets its own zone file containing multiple record types. When you modify records through the interface, DirectAdmin updates the underlying zone files and reloads the name server automatically.
Zone propagation typically takes 15 minutes to 24 hours globally. However, most visitors see changes within an hour when you manage records properly.
Accessing DNS Zone Editor
Navigate to your DirectAdmin dashboard and locate the DNS Management section. The exact layout varies by skin, but you'll find "DNS Management" or "DNS Zone Editor" in the main menu.
Click your domain name to enter the zone editor. You'll see a table showing existing DNS records with columns for Name, Type, Value, and TTL (Time to Live).
The interface displays system-generated records in gray and user-created records in standard text. Don't modify system records unless you understand the implications for email delivery and hosting functionality.
Creating and Managing A Records
A records point domain names to IP addresses. This is fundamental for web hosting since visitors need to reach your server's IP address.
To create an A record:
- Click "Add Record" and select "A Record"
- Enter the hostname (@ for root domain, www for subdomain)
- Input your server's IP address in the Value field
- Set TTL to 14400 (4 hours) for most hosting scenarios
- Click "Add" to save the record
For subdomain hosting, create A records pointing to the same IP or different servers. Many hosting customers use this for staging environments or separate applications.
Common A record configurations include:
- @ pointing to your main hosting IP
- www pointing to the same IP
- mail pointing to your email server IP
- ftp pointing to your FTP server if separate
If you're using Hostperl VPS hosting, you'll have a dedicated IP address for cleaner DNS management and better email deliverability.
Setting Up MX Records for Email
MX (Mail Exchanger) records tell other email servers where to deliver messages for your domain. Proper MX configuration ensures reliable email delivery.
DirectAdmin typically creates default MX records automatically. However, you may need custom MX records for external email services or specific routing requirements.
To configure MX records:
- Select "MX Record" from the record type dropdown
- Leave the Name field empty for root domain email
- Enter the mail server hostname in Value (e.g., mail.yourdomain.com)
- Set Priority (lower numbers = higher priority, typically 10 for primary)
- Set TTL to 14400 for standard email hosting
Multiple MX records provide email redundancy. Configure a primary server at priority 10 and backup servers at higher numbers like 20 or 30.
For businesses requiring reliable email hosting, our VPS solutions include dedicated resources and IP addresses that improve email deliverability compared to shared hosting environments.
CNAME Records for Subdomain Aliases
CNAME records create aliases that point one domain name to another. They're essential for services like CDNs, email providers, and third-party applications.
CNAME setup process:
- Choose "CNAME Record" as the record type
- Enter the subdomain name (without your domain)
- Input the target hostname in the Value field
- Set appropriate TTL based on how often the target changes
Popular CNAME configurations:
- www pointing to your root domain
- blog pointing to a WordPress hosting subdomain
- shop pointing to an ecommerce platform
- cdn pointing to your content delivery network
Remember: CNAME records cannot coexist with other record types for the same name. You can't have both A and CNAME records for "www", for instance.
TXT Records for Verification and SPF
TXT records store arbitrary text data. Modern hosting heavily relies on TXT records for domain verification, email authentication, and security policies.
Common TXT record applications:
- SPF records for email sender verification
- DKIM keys for email authentication
- Domain verification for Google Workspace or Microsoft 365
- Site verification for search engines and analytics
SPF record example: "v=spf1 include:_spf.hostperl.com ~all"
This tells receiving servers that your hosting provider's mail servers are authorized to send email for your domain. The ~all parameter means other servers should be treated as suspicious but not automatically rejected.
When adding TXT records, wrap values in quotes if they contain spaces or special characters. DirectAdmin handles most formatting automatically.
TTL Configuration for Performance
TTL (Time to Live) determines how long DNS resolvers cache your records. Shorter TTL means faster updates but higher DNS query load. Longer TTL reduces server load but delays propagation.
Recommended TTL values:
- 14400 (4 hours) for stable hosting environments
- 3600 (1 hour) during migrations or testing
- 300 (5 minutes) for rapid deployment scenarios
- 86400 (24 hours) for rarely-changing records like MX
Before major hosting changes, reduce TTL to 300 at least 24 hours in advance. This ensures quick propagation when you make the actual changes.
After successful migrations or updates, increase TTL back to normal values to reduce DNS server load and improve resolution performance for visitors.
Advanced Record Types
DirectAdmin supports additional record types for specialized hosting needs:
AAAA Records: Point domains to IPv6 addresses. Essential for modern hosting as IPv6 adoption increases. Format similar to A records but using IPv6 address format.
SRV Records: Define services and ports for applications. Often used for email clients, VoIP, and specialized applications. Format includes priority, weight, port, and target.
NS Records: Delegate subdomains to different name servers. Useful for separating application hosting from your main domain management.
Most hosting customers won't need these advanced records initially. Focus on A, MX, CNAME, and TXT records for standard website and email hosting.
Troubleshooting DNS Issues
Common DNS problems and solutions:
Changes not visible: Check TTL settings and wait for propagation. Use tools like dig or nslookup to verify records from different locations.
Email delivery problems: Verify MX records point to correct mail servers. Ensure SPF records include your hosting provider's mail servers.
Website not loading: Confirm A records point to active server IPs. Check that your hosting account is active and configured properly.
DirectAdmin includes a DNS zone validator. Use this tool before saving changes to catch syntax errors or conflicts.
For complex hosting setups, our managed VPS services include DNS management assistance. Our support team can help configure advanced record types and troubleshoot propagation issues.
Need reliable hosting with full DNS control? Hostperl's VPS hosting includes DirectAdmin control panels with complete DNS zone management capabilities. Our New Zealand-based support team assists with migrations, DNS configuration, and hosting optimization.
Explore our VPS hosting plans for professional DNS management and dedicated resources.
Frequently Asked Questions
How long does DNS propagation take in DirectAdmin?
DNS changes typically propagate within 15 minutes to 4 hours for most visitors. Global propagation can take up to 24-48 hours depending on TTL settings and cached records at various DNS resolvers worldwide.
Can I point my domain to multiple IP addresses?
Yes, create multiple A records with the same hostname pointing to different IP addresses. This provides basic load distribution and redundancy. DNS resolvers will rotate between the IPs automatically.
What's the difference between CNAME and A records?
A records point directly to IP addresses while CNAME records point to other domain names. Use A records for root domains and direct IP pointing. Use CNAME records for subdomains that should follow another domain's IP changes.
How do I backup my DNS zone configuration?
DirectAdmin includes zone file export options in the DNS management section. Export your zone files before making major changes. You can also document record configurations in your hosting management notes.
Why can't I create CNAME for my root domain?
DNS standards prohibit CNAME records at the root level because they conflict with required records like SOA and NS. Use A records for root domain pointing and CNAME only for subdomains like www or blog.
