Docs

Server Groups and Restarts

How to share DNS zones with a second nameserver, copy settings to other intoPanel servers, restart the server, and restart, stop or start single services.

6 min read Updated From the panel's guide

This page covers three admin menu sections: Server Groups (DNS Cluster and Settings Sync Group), Server Restart (Restart the Server Safely and Force Restart the Server), and Restart a Service.

DNS Cluster#

In the admin area, open Server Groups → DNS Cluster (DNS Cluster). A DNS cluster lets a second server answer for your domains, so that the domains still resolve when one server is down.

The form has two fields:

  • Servers that copy this server's zones: the IP addresses of your other nameservers, separated by commas or spaces (up to 8). They may fetch every zone from this server and are told about each change.
  • Server this one copies all zones from: set this on a second nameserver. Enter the IP address of the server where the accounts are.

To set up two nameservers on two servers:

  1. On the server with the accounts, enter the other server's address in the first field and click Apply.
  2. On the other server, install intoPanel (it needs no accounts). Open DNS Cluster there, enter the first server's address in the second field, and click Apply.
  3. Make sure port 53 (TCP and UDP) is open between the two servers.
  4. Point your nameserver names (such as ns1 and ns2) at the two servers, under Initial Server Setup and at your domain registrar.

New and removed zones follow by themselves.

Good to know:

  • Only IP addresses are accepted, not names.
  • A server cannot be both the one copied from and one that copies.
  • If the new settings are refused by the DNS server's configuration check, the old settings are put back and the page shows the error.

Settings Sync Group#

In the admin area, open Server Groups → Settings Sync Group (Settings Sync Group). It links this server to other intoPanel servers, so you can copy this server's settings out to them from here. Each server checks every value before it takes it.

The settings that can be copied are: Server Preferences; Apache, PHP, Database Server, Exim, Dovecot and FTP tuning; Greylisting; ModSecurity; Backup Settings; and Automatic SSL Options.

To add a server:

  1. On the other server, open API Tokens and make a token with full access.
  2. Here, click Add a Server.
  3. Enter the Server name or IP address. Add :port when its panel does not answer on port 7443.
  4. Enter the User the token belongs to (root by default).
  5. Paste the API Token (it starts with ipt_).
  6. Click Save. This server tests the token at once and remembers the other server's certificate.

To copy settings:

  1. Under Copy this server's settings to the group, tick the Settings to copy. Settings with nothing set here are greyed out.
  2. Under To these servers, tick the servers.
  3. Click Copy Settings.

The progress shows on the page. The Servers table shows each server's last copy and its result.

Good to know:

  • Backup Settings includes the remote backup destination and its login.
  • If the other server's certificate changes, copying is refused. Delete the server and add it again if the change is expected.
  • A group has at most 50 servers.
  • To bring settings in from another server instead, use the Service Settings tab of Server Migration.

Restart the Server Safely#

In the admin area, open Server Restart → Restart the Server Safely (Restart the Server Safely).

  1. Type the word reboot in the box.
  2. Click Restart the server.

The server shuts down its services in order and starts again. Every website, mailbox and the panel are unavailable for a minute or two. Reload the panel after that time.

The restart is refused while a panel task or a backup is still running. Wait for it to finish and try again, or use "Force Restart the Server" if the server no longer reacts normally.

Good to know:

  • Most changes do not need a server restart. To apply a change to one service, restart only that service under Restart a Service.

Force Restart the Server#

In the admin area, open Server Restart → Force Restart the Server (Force Restart the Server).

  1. Type the word force in the box.
  2. Click Reboot now, without waiting.

Use this only for a server that no longer reacts normally. Services are not asked to finish their work first. A running backup or task is cut off, and data being written at that moment can be lost. The panel is back in a minute or two.

Good to know:

  • Always try Restart the Server Safely first.
  • If the panel itself does not respond, restart the server from your provider's control panel or console instead.

Restart a Service#

In the admin area, open the Restart a Service section and choose a service:

  • Database Server (MariaDB)
  • DNS Server (BIND)
  • FTP Server (Pure-FTPd)
  • HTTP Server (Apache)
  • IMAP Server (Dovecot)
  • Mail Server (Exim)
  • PHP-FPM (all PHP versions)

Each page shows the service's state (Running, Not running, Failed or Not installed) with these buttons:

  • Restart and Stop when it is running.
  • Start when it is not running.

The PHP-FPM page has one row for each installed PHP version. Each page also links to that service's settings pages.

Restarting a service interrupts it for a moment:

  • Apache: websites answer again after a second or two.
  • Database server: websites that use a database show an error until it is back.
  • DNS server: answers pause briefly, and other nameservers keep answering.
  • FTP server: transfers in progress are cut off.
  • IMAP server: mail programs reconnect by themselves.
  • Mail server: mail being received is offered again by the sending server.
  • PHP-FPM: PHP pages of that version wait or fail for a second or two.

Stop keeps a service off until you start it again.

Good to know:

  • If a service does not restart, the message tells you to check systemctl status <service> on the server, for example in the Terminal.
  • Which services are monitored is set under Services and Monitoring.

SSH Server (OpenSSH)#

In the admin area, open Restart a Service → SSH Server (OpenSSH) (SSH Server (OpenSSH)). Click Restart SSH under Restart the SSH server.

SSH sessions that are open stay open. The SSH server can be restarted from the panel but never stopped, so you cannot lock yourself out.

Restart SSH after you change its configuration by hand on the server, so that the change takes effect.

Good to know:

  • Before you restart SSH after editing its configuration by hand, keep a session open, so that you can fix a mistake if new sign-ins fail.

Mailing Lists#

In the admin area, open Restart a Service → Mailing Lists (Mailing Lists). Unlike the other entries in this section, this page has nothing to restart. The lists are handled by the mail server itself; there is no separate list program (such as Mailman) to look after, and no list passwords.

The page lists every mailing list on the server with:

  • its address and account;
  • the number of members;
  • who may write to it: Anybody or Members only;
  • its owner.

A mailing list is one address that passes every message on to all its members. Clients make and change their lists in their own area, under Email. To change a list for a client, open the client's area from the account list (see Hosting Accounts).

Good to know:

  • The number of lists an account may have is set in its package (Mailing lists allowed).
Was this article helpful?

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