Docs

DNS

How to manage the DNS zones kept on this server, zone templates, mail records, nameserver checks, domain aliases and forwarding from the DNS section of the admin area.

12 min read Updated From the panel's guide

The DNS section of the admin area holds the tools for the DNS zones this server answers for. The server runs BIND, and it answers only for the domains hosted on it; it does not look up other names for anyone. Every website gets its own zone by itself when it is created (a subdomain gets its records in the parent zone of the same account), so most of these tools are for checking, tidying and bulk changes.

If BIND is not installed, the DNS pages say so; run the intoPanel installer again to install it. The nameserver names and the public address that new zones use are set under Server Setup → Initial Server Setup, and copying zones to a second nameserver is set up under Server Groups → DNS Cluster.

DNS Zones#

In the admin area, open DNS → DNS Zones (DNS Zones). The page lists every zone on the server with its owner (an account, or "root" for zones you created yourself) and its number of records.

  • Type part of a domain in Filter by domain and click Find to narrow the list.
  • + A Record, + CNAME Record and + MX Record open the zone with the add form already set to that type.
  • Manage opens the zone with all its records.
  • Create at the top leads to Add a DNS Zone.

Clients edit the zones of their own domains in their own area (DNS Records). As administrator you can open and change any zone here, including the zones of client accounts.

Good to know:

  • A zone holds at most 500 records.
  • The record types you can add are A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR, DNAME, TLSA, SSHFP and DS.
  • The serial number of a zone is raised by itself with every change, so secondary nameservers pick the change up.

Editing the records of a zone#

In the admin area, open DNS → DNS Zones (DNS Zones) and click Manage next to a zone. The zone page has three parts: the record form, the SOA settings and the list of records.

To add a record:

  1. Fill in Name: @ is the domain itself, ns1 means ns1.yourdomain, and so on.
  2. Choose the Type.
  3. Enter the Value, for example an IP address for an A record. For MX records write the priority first, such as 10 mail.example.com.
  4. Optionally enter a TTL in seconds (60 to 604800; 3600 when left empty).
  5. Click Add record.

To change a record, click Edit in its row, change the name, value or TTL (the type cannot be changed) and click Save the change. Delete removes a record at once.

The SOA record and default TTL form sets the zone's default TTL (used for records without their own), the administrator's email, and the refresh, retry, expire and minimum times that secondary nameservers and resolvers use. Click Save to store them.

Put the usual records back replaces every record of the zone with the standard set: nameservers, the website address for @, www and mail, an ftp alias, the MX record, SPF, and DKIM and DMARC where mail signing is set up, plus the records of your DNS Zone Templates. Records you added by hand are lost. Remove this zone appears only on zones that belong to no account.

Add a DNS Zone#

In the admin area, open DNS → Add a DNS Zone (Add a DNS Zone). Use it for a domain that is not a website on this server, such as your company's domain that carries the nameserver names (ns1, ns2). Websites get their zones by themselves, so you do not need this page for them.

  1. Enter the Domain, for example yourcompany.com.
  2. Click Add Zone.

The zone is created with the usual records, pointing to this server's public address, and opens so you can add more. It is listed with the owner "root".

Good to know:

  • A zone that already exists cannot be created again.
  • A name that lies inside another account's zone is refused; add the records to that zone instead.
  • The new zone only takes effect on the internet when the domain's registrar lists this server's nameservers. Check that with the Nameserver Check.

Delete a DNS Zone#

In the admin area, open DNS → Delete a DNS Zone (Delete a DNS Zone). The page lists every zone with a checkbox.

  1. Tick the zones you want to delete (the box in the header ticks all of them).
  2. If any of them belongs to a website (marked "website"), also tick Also delete the zones of websites I selected. Without this, website zones are skipped and reported as not done.
  3. Click Delete Selected Zones.

Deleting a zone stops this server, and its DNS cluster, from answering for that domain. A website whose zone is deleted stays on the server with its files, mail and databases, but its name no longer resolves here.

Good to know:

  • Deletion cannot be undone, but a website's zone can be rebuilt: create it again under Add a DNS Zone, or open the zone and use "Put the usual records back". Records you added by hand are not restored.
  • To remove only zones whose accounts are gone, use Clean Up DNS Zones instead.

Hostname Address Record#

In the admin area, open DNS → Hostname Address Record (Hostname Address Record). The page shows the server's hostname and one button, Add or correct the A record.

Clicking it points the server's own name (for example server1.yourcompany.com) at the server's main address by adding or correcting an A record in the zone the name lies in. A message tells you which zone was changed and which address was used.

This only works when the hostname lies in a DNS zone kept on this server, for example when yourcompany.com has a zone here. If it does not, you get a message saying so; add the A record where that domain's DNS is kept, such as at your registrar or DNS provider.

A correct A record for the hostname matters for the panel's own certificate, for mail (receiving servers check that the name the server greets with resolves) and for reverse DNS. The hostname itself is changed under Network → Change Hostname.

DNS Zone Templates#

In the admin area, open DNS → DNS Zone Templates (DNS Zone Templates). Here you add extra records that every new zone gets on top of the standard set (nameservers, the website's address, www, mail, FTP and the mail records).

To add a record to the template:

  1. Enter the Name, such as @ or webmail.
  2. Choose the Type: A, AAAA, CNAME, MX, TXT, SRV or CAA.
  3. Set the TTL in seconds (default 3600).
  4. Enter the Value. %ip% becomes the account's address and %domain% the zone's name. For MX write the priority first, for example 10 mail.%domain%.
  5. Click Add to the template.

Remove in a row takes that record out of the template.

Good to know:

  • A template holds at most 50 records.
  • NS and SOA records cannot be part of the template; nameservers are set under Initial Server Setup.
  • Existing zones are not changed. To apply the template to an existing zone, open it under DNS Zones and use "Put the usual records back", which also removes records added by hand.
  • A template record that duplicates one already in the zone is skipped.

Mail DNS Records#

In the admin area, open DNS → Mail DNS Records (Mail DNS Records). This is the same page as Email → Mail Deliverability. It shows, for each domain, whether its zone has the records that prove mail really comes from this server: SPF, DKIM (the signing key) and DMARC, and where its mail goes (MX).

The Mail records of each domain table reads the zones kept here. "Missing" means the zone has no such record. Add all missing records adds SPF, DKIM and DMARC to every zone that lacks them; zones with their own records keep them. A domain shown as "Inside another zone, or its DNS is not kept on this server" has no zone of its own here.

Run the check in the Check against live DNS box looks each domain up on the internet the way a receiving mail server does, and also checks the reverse DNS (PTR) of the server's sending address. A record that is set in the zone but shows a problem in the live check usually means the domain does not use this server's nameservers, or the change has not spread yet.

Reverse DNS is set by whoever provides the server's IP address, not in the panel; it should be the server's hostname. See Email for more on deliverability.

Mail Routing#

In the admin area, open DNS → Mail Routing (Mail Routing). The page lists every mail domain and whether its mail is handled On this server or By another server.

Choose "by another server" when a domain's MX record points to Google Workspace, Microsoft 365 or another mail host. Mail sent from this server to that domain (contact forms, other clients on the server) then goes out to that host instead of into a mailbox here, where nobody would read it.

To change one domain, click Handle elsewhere or Handle here in its row.

To let the panel work it out:

  1. Click Detect from the MX records. A column shows what the MX records say ("here", "elsewhere" or "unknown") and why.
  2. Check the result, then click Use the detected setting for every domain to apply it to all domains where it differs.

Detection counts an MX as "here" when it resolves to an address of this server, or to one of the trusted mail servers listed under Trusted Remote Server IPs. Clients can set the same thing for their own domains in their own area.

DKIM and SPF for All Domains#

In the admin area, open DNS → DKIM and SPF for All Domains (DKIM and SPF for All Domains). The page has one button, Add the missing mail records.

It goes through every zone on the server and adds the records that are missing:

  • SPF: a TXT record v=spf1 a mx ~all on the domain itself, when the zone has no SPF record yet.
  • DKIM: the TXT record with the domain's signing key, when mail signing is set up for it.
  • DMARC: a TXT record v=DMARC1; p=none at _dmarc, when there is none.

Zones that already have their own SPF or DMARC record are left as they are. A message tells you how many zones were changed.

New zones get these records automatically, so you mainly need this after a migration, after records were deleted by hand, or for zones created before mail signing was set up. To see the state of each domain first, open Mail Deliverability. The records only take effect when the domain uses this server's nameservers.

Nameserver Check#

In the admin area, open DNS → Nameserver Check (Nameserver Check) and click Run the report. The panel asks the internet which nameservers each domain really uses and compares them with the NS records in the zone kept here. This takes a few seconds per domain; up to 300 zones are checked.

The table shows, for each zone, its account, the nameservers named in the zone, the nameservers at the registrar, and a state:

  • Uses this server: the registrar's nameservers resolve to this server (or to a nameserver listed under Trusted Remote Server IPs). "Names differ from the zone" means they lead here but under other names than the zone's NS records.
  • Points elsewhere: the registrar names other nameservers, so the records kept here are not the ones visitors get.
  • Not registered or no answer: the domain has no nameservers on the internet, for example because it has expired or was never registered.

Use the report before moving websites, to find out which domains depend on this server's DNS, and when a client's DNS changes seem to have no effect.

Add a Domain Alias#

In the admin area, open DNS → Add a Domain Alias (Add a Domain Alias). A domain alias (also called a parked domain) shows the same website as an existing domain.

  1. Enter the Alias domain, for example example.net.
  2. In Shows the website, choose the website (main, addon or subdomain) and its account.
  3. Click Add the alias.

The alias is added to the website's settings and answers with the same content. If the alias domain is registered elsewhere, point its DNS at this server so visitors reach it.

Good to know:

  • The alias counts towards the account's limit for domain aliases set in its package.
  • All aliases on the server are listed under Account Lists → Domain Aliases (Domain Aliases).
  • Clients can add and remove aliases for their own websites in their own area.

Clean Up DNS Zones#

In the admin area, open DNS → Clean Up DNS Zones (Clean Up DNS Zones). The page has one button, Clean up now.

It looks for zones that still name an owner account which no longer exists on this server, for example after an account was removed by hand or a removal was interrupted, and deletes those zones. The message lists the zones that were removed, or says there was nothing to clean up.

Zones of existing accounts and zones you created yourself (owner "root") are never touched.

Good to know:

  • Removed zones are gone from this server and from the DNS cluster; this cannot be undone.
  • To delete particular zones yourself, use Delete a DNS Zone.

DNS Record Lifetime (TTL)#

In the admin area, open DNS → DNS Record Lifetime (TTL) (DNS Record Lifetime (TTL)). The TTL is how long other servers remember an answer before they ask again.

  1. In Zone, choose one zone, or All zones on this server.
  2. Enter the TTL (seconds), between 60 and 604800.
  3. Click Set the TTL.

Every record in the chosen zones gets the new TTL, except the nameserver (NS) records, which keep their own long life. The message tells you in how many zones the TTL changed.

A common use: lower the TTL to 300 a day before you move websites to a new server or new IP address, so the change is seen quickly, then set it back to 3600 or more afterwards. To change only one record's TTL, edit that record in the zone under DNS Zones.

Domain Forwarding#

In the admin area, open DNS → Domain Forwarding (Domain Forwarding). Here you send every visitor of a website to another address.

  1. Choose the Website.
  2. Enter the full address in Forward to, for example https://www.example.com/.
  3. Choose the Kind: Permanent (301) for a lasting move, Temporary (302) otherwise.
  4. Leave Keep the rest of the address ticked to send example.com/page to the same page at the new address; untick it to send every page to the address you entered.
  5. Click Forward the domain.

The forwarding is a redirect for / in the website's settings; the website's DNS is not changed, so the domain must still point at this server.

To change or stop a forwarding, open the account, sign in as the client and remove the redirect for / under the website's settings (Redirects).

Sync DNS Records#

In the admin area, open DNS → Sync DNS Records (Sync DNS Records). The page has one button, Sync all zones.

It writes every zone on this server again with a new serial number and reloads it. The other nameservers of your DNS cluster are told about the change and fetch a fresh copy of each zone. A message tells you how many zones were written.

Use it when a secondary nameserver is out of step, for example after it was offline, after you set up the cluster, or after zones were restored. Record contents are not changed.

The cluster itself is set up under Server Groups → DNS Cluster (DNS Cluster): there you list the servers that copy this server's zones, or the server this one copies from. Port 53 (TCP and UDP) must be open between them.

Was this article helpful?

Something missing? Ask in the community or open a ticket.