📌 Purpose & Quick Summary
The DNS Zone Editor provides full control over your domain's Domain Name System (DNS) zone files. You can create and manage essential record types—including A, AAAA, CNAME, TXT, MX, and SRV records—with custom TTL values. Additionally, it features an Export for Cloudflare utility that outputs standard BIND zone format for instant 1-click import into Cloudflare DNS.
Figure 17: DNS Zone Editor showing record management form, active records ledger, and Cloudflare export button.
🖥️ Interface Tour & Elements
- Domain Selector: Dropdown to select which domain zone to inspect and manage.
- Add DNS Record Form:
- Type Dropdown:
A,AAAA,CNAME,TXT,MX,SRV. - Name (Host): Subdomain or
@for root domain. - TTL (Time to Live): Duration in seconds (e.g.
3600). - Value (Target): IP address, hostname, or text string.
- Priority: Required for
MXrecords (e.g.10).
- Type Dropdown:
- Active DNS Records Table: Ledger of all compiled records with inline Edit modals and Delete actions.
- Export for Cloudflare Button: Generates a standard RFC 1035 BIND zone file ready for 1-click import into Cloudflare.
🛠️ Step-by-Step Instructions
Step 1: Adding an A or CNAME Record
- In the sidebar, click DNS Zone Editor (icon:
fa-network-wired). - Select your domain from the dropdown.
- In the Add Record form:
- Select A from the Type dropdown.
- In Name, enter
sub(forsub.yourdomain.com). - In Value, enter the target IPv4 address (e.g.
159.198.42.18). - Leave TTL at
3600.
- Click Deploy Record. The BIND/PowerDNS daemon recompiles the zone file immediately.
Step 2: Exporting Zone for Cloudflare
- Click the Export for Cloudflare button at the top-right.
- A modal displays the complete BIND-formatted zone file.
- Click Copy to Clipboard or Download .txt.
- In Cloudflare Dashboard, go to DNS -> Records -> Import, and upload the file to mirror all records instantly.
⚙️ Complete Field & Parameter Reference Table
| Record Type | Common Use Case | Value Example | Priority Field |
|---|---|---|---|
| A | Pointing domain/subdomain to IPv4 address | 159.198.42.18 |
Not applicable |
| AAAA | Pointing domain to IPv6 address | 2001:0db8::ff00:42 |
Not applicable |
| CNAME | Aliasing domain to another hostname | ghs.googlehosted.com |
Not applicable |
| TXT | Verification (Google, Facebook) & SPF/DKIM | "v=spf1 mx ~all" |
Not applicable |
| MX | Mail server routing | mail.yourdomain.com |
Required (10, 20) |
❓ Troubleshooting & Common Errors
1. Changes Not Visible (DNS Propagation Delay)
- Cause: Local ISP DNS resolvers cache previous records until the old TTL expires.
- Solution: Allow 10 to 60 minutes for propagation, or verify using public DNS tools like
dnschecker.org.