In this article from the TripleZero iT knowledge base we explain: How do I use the DNS Zone Editor in DirectAdmin?. We describe the purpose, the preparation and a clear method that you can follow step by step.
This manual is written for customers of TripleZero iT and assumes common configurations on shared hosting, reseller environments and control panels such as DirectAdmin, CyberPanel and Plesk.
What you need
- Access to DirectAdmin or the TripleZero iT customer panel.
- Your domain name and any login/mailbox details.
- A current browser and, where applicable, FTP/SSH access.
- Preferably a recent backup before making structural changes.
Step-by-step approach
- Log in to the appropriate panel at TripleZero iT and select the domain or account affected by the change.
- Check that you have the correct environment (production vs. test) and note the current settings.
- Perform the action corresponding to “How do I use the DNS Zone Editor in DirectAdmin?”. Work calmly and do not change multiple critical options at the same time.
- Save changes and test the result: website, email or DNS — depending on the subject.
- Document what you changed so you can roll back later or help support more quickly.
Deeper explanation
The topic “How do I use the DNS Zone Editor in DirectAdmin?” often affects multiple layers: DNS, web server, mail server, application (e.g. WordPress) and account limits. Problems usually arise when one layer is changed without checking the others.
For TripleZero iT, we recommend first verifying that DNS points to the correct name servers, then checking control panel settings, and only then changing application settings (plugins, themes, .htaccess).
DNS and registration aspects
In this topic, DNS or domain registration plays a central role. Check name servers, TTL and whether changes are already visible worldwide before concluding that something “doesn't work”.
Preferably work with a single source of truth for DNS: either TripleZero iT name servers, or an external DNS provider — not both half-configured.
DNS records in practice
Open DNS management in the customer panel or DirectAdmin/CyberPanel/Plesk. Change one record at a time, write down the old value, and wait for propagation before concluding that something failed.
For CNAME: do not use CNAME on the apex (@) unless your provider supports ALIAS/ANAME. A records point to an IPv4 address; AAAA to IPv6.
Post-completion checklist
- Does the website work over HTTP and HTTPS without certificate errors?
- Are test emails delivered and not marked as spam?
- Are limits (disk, inodes, bandwidth) still within the package limits?
- Are there no unintentional redirects, firewall blocks or PHP errors in the logs?
Common bottlenecks
- DNS propagation: changes are not immediately visible everywhere.
- Wrongly selected domain or user in a reseller environment.
- Cache (browser, CDN, LiteSpeed/OpenLiteSpeed, WordPress plugins) showing old content.
- Missing permissions on directories or wrong document root.
When to enable support
If you get stuck after these steps — for example with persistent mail errors, SSL problems, or an unreachable site — open a ticket at TripleZero iT. Please include domain name, time, error message (screenshot or exact text) and what you have already tried.
Do you still have questions after following these steps? Contact TripleZero iT support via the ticket system or email. Always mention your domain name and a clear description of the problem, so that we can help you faster.
Also view other articles in the knowledge base for additional explanations about hosting, email and security.