Appearance

Managing a domain ​

This process covers adjusting the settings of a domain that has already been added, and syncing the matching DNS zone with the hosting server.

Step-by-step guide ​

1. Sign in to the customer portal ​

Sign in with your account in the customer portal.

2. Open the domains section ​

Open the desired hosting package and navigate to:

Domains

3. Select the domain ​

Click the relevant domain in the list, or use the Edit action.

4. Adjust the settings ​

In the Edit Domain section you can change:

  • Description
  • Documentroot – the directory within the web space the domain is served from (relative to your hosting package's main directory)
  • OpenBasedir and Server Alias – technical options that are usually not needed
  • Let's Encrypt – enables the automatic SSL certificate
  • SSL Redirect – automatically redirects requests from http:// to https://
  • Email Only – the domain is used for email only and does not serve a website

Click Save afterwards.

5. Sync the DNS zone (optional) ​

The Sync DNS Zone section shows the primary and secondary nameserver the domain should be connected to. Click Sync now to automatically create or update the matching DNS records (A, AAAA, MX, and SPF/DMARC TXT records) for this domain.

Note

Syncing is only possible for first-level domains (e.g. example.com, not www.example.com). If no matching DNS zone exists yet, a new one is created automatically. Any existing, differing A, AAAA, MX or SPF/DMARC TXT records for this name are replaced in the process.

Follow-up checks ​

After saving, check:

  • that the website is still reachable under the domain
  • that the SSL connection works correctly
  • after a sync, that the DNS records in the associated DNS zone are set correctly

Common issues ​

Website is unreachable after the change ​

Possible causes:

  • the document root points to a directory that does not exist
  • SSL redirect was enabled while no valid certificate is present yet

DNS zone does not sync ​

Possible causes:

  • the domain is not a first-level domain
  • the matching DNS zone belongs to another team
  • a name in the target domain is already used by an unrelated, unassigned zone