DNS Zone — What It Is, Which Records It Holds and How to Manage It

Nodea is a hosting company based in Leszno, Poland, offering hosting and domain registration — configuring DNS zones is part of our daily support work. Below we explain, from a practitioner's angle, what a DNS zone is, which records it holds, how it works and how to manage it in the DirectAdmin panel. If you are only just registering a domain, you configure its zone right after purchase within the DNS system.

What is a DNS zone?

A DNS zone is a carved-out part of the DNS system that stores and manages the records of a single domain — it decides where the internet routes that domain's traffic.

Put simply: a DNS zone is a set of instructions telling the internet where to send a given domain's traffic. Thanks to a correctly configured DNS zone, the website, e-mail and other services tied to the domain all work — each of them relies on a different record in the zone.

It is worth telling two concepts apart. A DNS zone is the configuration, that is the data itself (the set of records). A DNS server is the machine that hosts that zone and answers queries from the internet. In other words: the zone is what is written down, the DNS server is what serves it. The DNS system itself is the overarching, global infrastructure — a DNS zone is a single element of it, responsible for one domain.

Which records does a DNS zone contain?

A DNS zone contains records: A points the domain to an IPv4 address, MX handles e-mail, and CNAME creates an alias to another domain name. These are the most used entries, but there are more record types.

• A record — points the domain to the server's IPv4 address.
• AAAA record — points the domain to an IPv6 address.
• MX record — indicates the servers that handle the domain's e-mail.
• CNAME record — creates an alias pointing to another domain name (e.g. www to the main domain).
• TXT record — stores text data: SPF, DKIM and DMARC records and entries verifying domain ownership.
• NS record — indicates the name servers responsible for serving the zone.
• SRV record — defines the location of specific services in the domain (e.g. a messenger or VoIP).

The records can be grouped by function. Pointing records (A, AAAA, CNAME, NS) route traffic and define name servers. Mail records (MX and, stored in TXT: SPF, DKIM, DMARC) handle and authenticate e-mail. If you are setting up a mailbox, you will need the SMTP/IMAP server addresses, which you configure alongside the MX record.

What are the A record and AAAA record for?

The A record points the domain to an IPv4 address (e.g. 203.0.113.10), and the AAAA record does the same for an IPv6 address (e.g. 2001:db8::1). Both point the domain to a server — they differ only in the version of the addressing protocol. The A record is the most frequently edited entry in the zone: it decides which server your site answers from when someone types the domain into a browser.

How does a DNS zone work?

A DNS zone works like a signpost: when someone enters a domain address, the DNS system reads its records and routes the traffic to the right server.

The mechanism runs step by step. When a user types a site address into the browser, the DNS system checks the records in that domain's DNS zone to determine where to send the query. The A record points to the web server's IP address — that is how the user reaches the site. E-mail works the same way: when someone sends a message to an address in your domain, mail servers read the MX record to learn which server receives e-mail for that domain.

The whole DNS zone is hosted on the DNS servers declared with the domain registrar (in the NS records). Those servers answer queries from all over the world. After buying and configuring the zone, the next step is often pointing the domain to hosting — that is, setting the A record so it points to the server where your site lives.

How long does DNS zone propagation take?

Propagation of DNS zone changes takes from a few minutes up to 24 hours — the time depends on the record's TTL setting.

After each record edit, the change does not appear worldwide instantly. DNS propagation has to happen — the spread of the new data across servers on the internet. The pace of this process is set by the TTL (Time to Live) — the parameter defining how long intermediate servers keep a record in their cache before fetching a fresh version. The lower the TTL, the faster changes reach users.

Practical advice: after editing a record, do not panic when the site or mail does not yet work under the new address. Wait up to 24 hours before reporting a problem — in most cases the change propagates much sooner.

What does a sample DNS zone show?

A sample DNS zone contains an A record with the server's IP address, an MX record with the mail server, NS records with name servers and an SOA record with the refresh time (e.g. 3600 seconds).

A simplified zone for the domain example.com looks like this:

• example.com. SOA ns1.nodea.pl. admin.example.com. (serial number; refresh 3600) — the zone header with metadata,
• example.com. NS ns1.nodea.pl. — the primary name server serving the zone,
• example.com. NS ns2.nodea.pl. — the backup name server,
• example.com. A 203.0.113.10 — the domain points to the web server's IPv4 address,
• example.com. MX 10 mail.example.com. — mail goes to the indicated server (the number 10 is the priority),
• www.example.com. CNAME example.com. — the www alias leads to the main domain.

The SOA record (Start of Authority) opens every zone: it stores the name of the primary name server, the administrator's address, the serial number and the zone refresh time — 3600 seconds, for example. Labelling each line turns theory into practice: you can see exactly which entry handles the site, which the mail and which the name servers.

How to manage a DNS zone in the panel?

To manage a DNS zone in the panel, go to DirectAdmin › Account Management › DNS Management — you will see all your domain's records ready to edit.

Once inside DNS Management you see the zone's default configuration view: a list of the existing A, MX, NS and CNAME records tied to the domain along with their values. This is where you add new entries and edit existing ones. The DirectAdmin panel replaces manual zone-file editing with a convenient form.

How to add or edit an A record:

1. Go to DirectAdmin › Account Management › DNS Management for the chosen domain.
2. In the record-adding section select the A type.
3. In the name field enter the name (e.g. the main domain or a subdomain), and in the value field the server's IPv4 address.
4. Confirm — the new A record appears in the list and starts routing traffic once propagation completes.

How to add or edit an MX record:

1. In the same DNS Management view select the MX record type.
2. Enter the mail server name (e.g. mail.yourdomain.com) and the priority (e.g. 10).
3. Save — from now on the domain's mail will be routed to the indicated server.

If the configuration gets tangled, the zone can be reset. In the DNS Management view use the option to restore the default configuration — the reset removes your custom records and recreates the default A, MX and NS entries tied to the account. It is a safe starting point when you want to configure the zone from scratch.

How to add a DMARC record to a DNS zone?

You add a DMARC record as a TXT record in DNS Management — it is a mail-authentication entry that reduces spoofing of your domain.

1. Go to DirectAdmin › Account Management › DNS Management for the domain.
2. Add a new record of type TXT.
3. In the name field enter _dmarc, and in the value field the DMARC policy, e.g. v=DMARC1; p=none; rua=mailto:reports@yourdomain.com.
4. Save the record — after propagation, receiving servers will start applying your DMARC policy.

DMARC is one of three mail-authentication records (alongside SPF and DKIM), which you also store as TXT records in the same DNS zone.