How the DNS zone module works in ISPmanager 6
When a site is created, ISPmanager 6 automatically sets up a DNS zone for the domain and fills it with basic records: an A record pointing to the server's IP, an MX record for the local mail server, SPF, and records for webmail. You can manage the zone manually in "Domains → DNS Zones" without touching named configuration files in the console.
The zone is stored in BIND format and served by the named service on the panel server, unless you have switched the domain to external DNS servers. The process of connecting the domain itself to the server is described in the article creating a site in ISPmanager 6.
Which record types does ISPmanager 6 support
The panel supports all the main types of DNS resource records.
| Record type | Purpose | Example value |
|---|---|---|
| A | binds the domain to IPv4 | 203.0.113.10 |
| AAAA | binds the domain to IPv6 | 2001:db8::1 |
| CNAME | alias to another name | example.com |
| MX | domain's mail server | 10 mail.example.com |
| TXT | SPF, DKIM, verification | v=spf1 mx ~all |
MX record priority is set in a separate field: the lower the number, the higher the server's priority for mail delivery.
How to add and change a domain record
Changing a record takes a few steps in the panel interface.
- Open "Domains → DNS Zones" and select the domain you need.
- Click "Create record" and specify the type, name, and value.
- Set the record's TTL — its lifetime in resolver caches, usually 3600 seconds.
- Save the change: the panel will update the zone file and reload named.
For subdomains, it is enough to specify the name without the root domain: a record named "shop" will create shop.example.com automatically.
How to verify that a record has updated
DNS records do not propagate instantly because of caching on intermediate resolvers. You can check the current state of the zone directly on the server:
dig @127.0.0.1 example.com A +short
To see what external DNS servers see, query the same record type from a public resolver:
dig @8.8.8.8 example.com MX +short
If the result still differs from what you expect after more than a day, check the TTL of the old record and make sure the domain is actually delegated to your provider's NS servers.
Moving a zone to external DNS servers
If a domain's DNS is served not by ISPmanager but by a third-party service such as Cloudflare, you can disconnect the zone in the panel from named and keep it only for reference. In this case, all record changes must be made in the external DNS provider's panel, not in ISPmanager 6 — otherwise the edits simply will not apply.
When moving back — from external DNS to the panel server again — do not forget to recheck the NS records at the domain registrar, otherwise resolvers will keep querying the old servers. The same logic applies during a full site move: the process is described in the article moving a site between ISPmanager 6 servers.
Common mistakes when working with DNS zones
Most domain issues are not caused by the panel itself, but by carelessness when entering records.
- A trailing dot in a CNAME value is missing or, conversely, extra — the record resolves incorrectly.
- An MX record points to an IP address instead of a domain name — mail servers reject such a record.
- TTL is set too high before a planned IP change — rollback takes extra hours.
Checklist before changing a live zone: lower the record's TTL in advance, save the current values in case you need to roll back, make the change, and verify it with the dig command from two different resolvers before considering the move complete.