Appearance

DNS ​

This documentation describes how to manage DNS zones in the customer portal.

A DNS zone groups together all DNS records (e.g. A, AAAA, MX or TXT records) for a domain and defines how that domain is reachable on the internet – for example which server serves a website or which server accepts email for the domain.

Contents ​

This documentation covers:

Scope ​

DNS management is done in the customer portal via the DNS Zone menu item in the Products section.

Every DNS zone is its own product, independent of Hosting or Domain products. A zone is automatically populated with matching records when a hosting package is linked to a domain using the Sync DNS Zone feature. It can, however, also be ordered on its own and maintained manually.

Creating a new DNS zone ​

  1. Open DNS Zone in the main menu.
  2. Click Order Product in the top right corner.
  3. Follow the order process to order a new DNS zone for your domain.

Once the order is complete, the zone appears in the DNS Zone overview.

Zone overview ​

The DNS Zone list shows all existing zones with the following columns:

  • Name – the domain name of the zone
  • Team – the team the zone belongs to
  • Product – the associated product

Open a zone to see its detail view, which shows:

  • the zone's name
  • the DNS propagation status (DNS Propagated or DNS Propagation Pending)
  • below that, the table with all DNS records for this zone (see Managing DNS records)

Follow-up checks ​

After creating or changing a zone, check:

  • whether the DNS records are set correctly
  • whether your domain's nameservers point to our DNS servers
  • whether the DNS records resolve correctly

You can verify DNS records with tools like dig, nslookup or Google Public DNS.

Our status page lets you check the availability of our DNS servers.

Common issues ​

Domain does not resolve, email is not sent or received ​

Possible causes:

  • the domain's nameservers do not point to our DNS servers
  • the DNS zone has no records or contains incorrect records
  • the DNS change has not fully propagated yet (propagation can take up to 24 hours)
  • a firewall or network issue is blocking requests to the DNS servers