DNS Zone Editor: Managing A Records, MX, and TXT Entries

The Domain Name System, or DNS, is a core part of every domain. It translates readable domain names such as yourdomain.ch into technical destination information, for example an IP address or the responsible mail server. Without correctly configured DNS records, websites, email addresses, subdomains and external services such as Microsoft 365, Google Workspace, newsletter platforms and verification tools may not work reliably.

In cPanel, this is handled through the Zone Editor. It allows you to manage DNS records for domains that exist in your hosting account. The most commonly used record types are A records, CNAME records, MX records and TXT records. This article explains what these records mean, when to use them and what you should consider before making changes.

What Is a DNS Zone?

A DNS zone is the area where the DNS records of a domain are stored and managed. You can think of it as a technical address file. It contains information such as which IP address belongs to the website, which server accepts email and which external services may verify or use the domain.

When a visitor opens your website, their device does not immediately ask your website directly. It first asks the DNS system: “Where does this domain point?” The answer comes from the DNS records. This is why DNS is essential for domains, web hosting and email.

The Most Important DNS Records at a Glance

Depending on the cPanel version and your account permissions, the Zone Editor may show different DNS record types. The following record types are the most common in practice:

A Record: Pointing a Website to an IP Address

The A record is one of the most important DNS records. It connects a domain name to an IPv4 address. If your website is hosted by CURIAWEB, the A record usually points to the web server of your hosting package. If your website is hosted externally, for example on another server or with an external website builder, a different A record may be required.

Typical examples of A records:

• yourdomain.ch points to the IP address of your web server.
• shop.yourdomain.ch points to a separate server for an online shop.
• app.yourdomain.ch points to an external web application.

CNAME Record: Pointing One Name to Another Hostname

A CNAME record points one DNS name to another hostname. Instead of entering an IP address directly, you enter a target such as target.provider.com. The CNAME then follows that target.

A typical use case is the www subdomain. Often, www.yourdomain.ch points via CNAME to yourdomain.ch. External services also frequently require CNAME records, for example website builders, shop systems, newsletter platforms or verification systems.

Important: A CNAME should not be used together with other record types for the exact same name. If an external provider gives you precise DNS instructions, copy them carefully.

MX Record: Defining the Mail Server for Your Domain

The MX record defines which server accepts email for your domain. When someone sends a message to info@yourdomain.ch, the MX records are checked to determine which mail server is responsible for that domain.

MX records are especially important if you do not use the hosting server for email but instead use an external provider such as Microsoft 365, Google Workspace or a specialized mail service. In that case, the provider usually gives you exact MX values that must be added to DNS.

What Does MX Priority Mean?

MX records have a priority. The lower the value, the higher the priority. A mail server with priority 0 or 10 is used before a mail server with priority 20. Multiple MX records may be useful when a provider operates primary and secondary mail servers.

TXT Records: Verification, SPF, DKIM and DMARC

TXT records contain text information that external services or mail servers can read. Although a TXT record may look simple, it is very important in practice for security, email deliverability and domain verification.

Common uses for TXT records include:

• Domain verification: Services such as Google Search Console, Microsoft 365 or other platforms use TXT records to confirm that you control the domain.
• SPF: Defines which servers are allowed to send email on behalf of your domain.
• DKIM: Enables cryptographic signing of outgoing email, provided your mail service supports and configures it.
• DMARC: Tells receiving mail servers how to handle messages that fail SPF or DKIM checks.

SPF requires special care: normally, a domain should only have one SPF TXT record. Multiple separate SPF records can cause problems. If several services are allowed to send email for your domain, they should be combined into a single valid SPF record.

Step by Step: Adding a DNS Record in cPanel

1. Log in to your cPanel account.
2. In the Domains section, open the Zone Editor.
3. Find the required domain in the list.
4. Click Manage next to the domain.
5. Click Add Record or select the desired record type directly if cPanel shows this shortcut.
6. Enter the name, for example www, shop or the full domain.
7. Check the TTL value. If you have no special instructions, the default value can usually be kept.
8. Select the correct type, such as A, CNAME, MX or TXT.
9. Enter the target value, such as an IP address, hostname, mail server or verification text.
10. Click Save Record.

Step by Step: Editing an Existing DNS Record

1. Open the Zone Editor in cPanel.
2. Click Manage next to the relevant domain.
3. Find the record you want to change.
4. Use the filter or search function if needed to filter by A, CNAME, MX or TXT records.
5. Click Edit next to the desired record.
6. Change the value carefully.
7. Save the change.
8. Afterwards, check whether the website, email or external service still works correctly.

What Does TTL Mean?

TTL stands for Time To Live. It defines how long DNS resolvers may cache a record. A common value is 14400 seconds, which equals four hours.

A lower TTL can be helpful for planned migrations because changes may be picked up faster. A higher TTL reduces DNS queries and is common for stable records. If you are not planning a special migration, the default value in cPanel can usually be left unchanged.

DNS Propagation: Why Changes Are Not Always Visible Immediately

DNS changes are not always visible worldwide immediately. Many internet providers, operating systems, browsers and DNS resolvers cache DNS responses for a certain period of time. This process is often referred to as DNS propagation.

In many cases, changes become visible within minutes or hours. Depending on TTL, provider, cache and DNS structure, it may take longer. During this period, some visitors may already see the new configuration while others still receive the old DNS answer.

Common Mistakes in the DNS Zone Editor

1. Changing DNS in cPanel while external nameservers are active

If your domain uses external nameservers, changes in the cPanel Zone Editor may have no effect on public DNS resolution. First check where the authoritative DNS zone for your domain is managed.

2. Incorrect A record

An incorrect A record can make your website point to the wrong server or become unavailable. Only use IP addresses provided by the responsible hosting provider or service provider.

3. MX records without matching email configuration

MX records alone are not always enough. If you use an external mail service, additional SPF, DKIM and DMARC records are often required. The domain must also be configured correctly with the mail provider.

4. Multiple conflicting SPF records

Multiple separate SPF records for the same domain can cause problems. A single correctly combined SPF record is usually the better solution.

5. Misunderstanding the final dot in hostnames

DNS systems often use fully qualified domain names with a final dot, for example mail.yourdomain.ch.. Depending on the field, cPanel may add or interpret this automatically. Follow external provider instructions carefully and check whether the target is meant to be a full hostname.

When Should You Contact CURIAWEB Support?

DNS is technically sensitive because small changes can have major effects. Contact CURIAWEB Support if you are unsure whether a record is correct, if your website is no longer reachable after a change or if email suddenly stops arriving.

Careful review is especially useful when switching to external services such as Microsoft 365, Google Workspace, external shop systems or website builders. Ideally, send the DNS instructions from the external provider to support so the records can be checked accurately.

Frequently Asked Questions About the DNS Zone Editor

How long does it take for a DNS change to become active?
Changes are often visible within minutes or hours. Depending on TTL, DNS cache and provider, however, it may take longer until the change is visible everywhere.

Can I safely delete DNS records?
No. Only delete records if you are sure they are no longer needed. Deleting an MX record, for example, can affect email delivery.

Why does my website still point to the old server after a DNS change?
Possible causes include DNS cache, an unexpired TTL value, external nameservers or an incorrectly configured record.

Can CURIAWEB check my DNS zone?
Yes, CURIAWEB Support can check your DNS configuration if the domain and zone are manageable. For external DNS providers, access or screenshots of the settings may also be required.