Among the DNS terms you will encounter, ‘zone file’ is one that sounds deeply technical but describes something quite concrete: the single text file that holds every DNS record for a domain. It is where your domain’s A records, MX records, and all the rest actually live, and it is the authoritative source that answers the internet’s questions about your domain. This entry in the DNS vocabulary explains the concept clearly and shows how it fits alongside the other terms you already know.

This guide explains what a zone file is in DNS: what it contains, what a DNS ‘zone’ means, the key record types inside it, the SOA record at its head, where the file lives and how you actually interact with it, and how it relates to the wider DNS terms. It complements our fuller walkthrough of the DNS zone file, placing the concept precisely within the DNS terminology so the whole picture connects.

What a zone file is

A zone file is a text file, stored on a DNS server, that contains all the DNS records and settings for a specific domain. It is the authoritative master list that defines how your domain behaves in the DNS — where its website resolves, where its email is delivered, and every other instruction attached to the name. In short, it is where your domain’s DNS records actually live, gathered in one file.

Every individual record you might set for a domain — an A record pointing to a server, an MX record for email, a TXT record for verification — is an entry within this one zone file. When the wider internet needs an answer about your domain, that answer is served from the zone file held on your domain’s authoritative nameserver.

So a zone file is the concrete home of your domain’s DNS configuration: a single file that is the source of truth for the whole domain. As a term in the DNS vocabulary, it names the container that holds all the records — which is why understanding it ties together the other DNS terms like records, nameservers, and TTL that describe what is inside and around it.

What a DNS ‘zone’ means

To understand a zone file, it helps to pin down the word ‘zone.’ A DNS zone is the portion of the domain name system that a particular nameserver is responsible for — the slice of the namespace it has authority over. For most domain owners, the zone is simply your domain and everything under it, such as example.com and its subdomains.

The zone file, then, is the file that holds the records for that zone. If you own a domain, your zone file contains the records for the domain itself, its www version, any subdomains, and any other names within your domain that you have configured. The ‘zone’ is the administrative area; the ‘zone file’ is the file of instructions for it.

This is why ‘zone’ and ‘domain’ are often used almost interchangeably in everyday hosting contexts, even though technically a zone is the area a nameserver manages. For practical purposes, your zone file is the record list for your domain. Understanding this makes the term legible: a zone file is the file of DNS records for the zone — your domain — that a nameserver is authoritative for.

The records inside a zone file

A zone file is made up of individual DNS records, and a handful of types do the essential work. These are the entries you will find inside:

• A and AAAA records: point the domain to its web server’s IPv4 or IPv6 address.
• MX records: direct email for the domain to the correct mail server.
• CNAME records: point one name (like an alias or subdomain) to another domain name.
• TXT records: hold text used for verification and email security (such as SPF, DKIM, and DMARC).
• NS records: list the authoritative nameservers responsible for the domain.

Each record has a TTL (time to live) controlling how long it is cached elsewhere before being rechecked. Together these records define everything the internet needs to know about your domain — where its website and email go, how it verifies itself, and which nameservers serve it. Recognising these record types is what makes any zone file readable, since the file is simply an ordered collection of them.

The SOA record at the head

Every zone file begins with one special, mandatory record: the SOA, or Start of Authority. It is always the first record in the file and marks the beginning of the zone’s authority, holding the administrative metadata that governs the whole zone rather than routing any particular kind of traffic.

Inside the SOA you will find details like the primary (master) nameserver for the zone, a responsible contact, a serial number that tracks changes to the file, and timing values that control how secondary nameservers refresh their copies of the zone. It is essentially the zone’s identity and housekeeping record — the administrative header that sits above all the routing records.

You rarely edit the SOA directly, as your host manages it, but knowing it exists explains the structure of a zone file: an administrative header (SOA), then the nameservers responsible (NS records), then the routing records (A, MX, CNAME, TXT). The serial number in the SOA is how the DNS system knows the zone has changed and needs to be re-read. The SOA is the quiet backbone that makes the rest of the zone function.

Where it lives and how you use it

A zone file lives on your domain’s authoritative nameserver — the server responsible for answering questions about your domain — which in practice means wherever your DNS is managed: your host, your registrar, or a DNS service, depending on where your nameservers point. That is the machine holding the file that the internet queries.

Crucially, in the modern world you almost never edit the raw zone file by hand. Instead, your provider gives you a DNS zone editor — a friendly table where you add, change, and remove records with simple form fields. Behind the scenes, those changes are written into the zone file, but you interact with a clean interface rather than raw text syntax.

So understanding the zone file matters even though you may never see it as a file: every time you add an A record to point your domain, or MX records for email, in your DNS panel, you are editing your zone file through that interface. The concept explains what the panel is really doing, and it clarifies a common point of confusion — that your changes only count in the zone file on the nameservers your domain actually uses, which is why editing DNS in the wrong place has no effect.

How it fits the DNS vocabulary

As a term in the DNS vocabulary, ‘zone file’ sits naturally alongside the others and helps them connect. Nameservers are the servers that hold and serve your zone file; DNS records are the individual entries inside it; the SOA is its mandatory header; TTL governs how long each record is cached; and propagation is the delay while a changed zone spreads across the internet’s caches.

So the zone file is the container that ties these terms together: it is the file, held on your nameservers, made up of records (headed by the SOA, each with a TTL), whose changes propagate outward when you edit it. Understanding it gives the other DNS terms a home — they describe what is inside the file, where it lives, and how changes to it behave.

For a fuller, beginner-friendly walkthrough of the zone file — including reading a real one and how it maps to your DNS panel — our dedicated DNS zone file guide covers it in depth. As a terminology entry, though, the essential point is this: a zone file is the authoritative text file of all your domain’s DNS records, living on your nameservers and edited through a friendly panel, and it is the concept that connects nameservers, records, the SOA, TTL, and propagation into one coherent picture of how your domain works.

FAQs

What is a zone file in DNS?

A zone file is a text file, stored on a DNS server, that contains all the DNS records and settings for a specific domain. It’s the authoritative master list defining how your domain behaves — where its website and email go, plus verification and other instructions. In short, it’s where all your domain’s DNS records actually live, in one file.

What does ‘zone’ mean in DNS?

A DNS zone is the portion of the namespace a particular nameserver is responsible for — the slice it has authority over. For most owners, the zone is simply your domain and everything under it. So the zone file is the file of records for that zone — effectively the record list for your domain and its subdomains.

What records are in a zone file?

An SOA (Start of Authority) record first, then NS records for the responsible nameservers, and the routing records: A and AAAA (website IPs), MX (email), CNAME (aliases), and TXT (verification and email security like SPF, DKIM, DMARC). Each has a TTL controlling how long it’s cached. Together they define everything about the domain.

What is the SOA record in a zone file?

The SOA (Start of Authority) is the mandatory first record in every zone file. It marks the start of the zone’s authority and holds administrative details — the primary nameserver, a contact, a serial number tracking changes, and refresh timing values. Your host manages it, and it’s the zone’s housekeeping backbone above the routing records.

Where is a zone file stored and how do I edit it?

On your domain’s authoritative nameserver — wherever your DNS is managed (host, registrar, or DNS service), depending on where your nameservers point. You almost never edit the raw file; instead your provider gives you a DNS zone editor, a table where you add and change records with form fields, and those edits are written into the zone file for you.

How does a zone file relate to other DNS terms?

The zone file is the container that connects them: nameservers hold and serve it, DNS records are the entries inside it, the SOA is its header, TTL governs how long each record is cached, and propagation is the delay while a changed zone spreads across the internet. Understanding the zone file gives the other DNS terms a home.

The bottom line

A zone file in DNS is the text file, stored on your domain’s authoritative nameserver, that holds every DNS record and setting for your domain — the authoritative source of truth for where your website resolves, where your email is delivered, and how the domain verifies itself. A ‘zone’ is simply the portion of the namespace a nameserver is responsible for, which for most owners means your domain and its subdomains, so the zone file is effectively your domain’s complete record list. It opens with the mandatory SOA record — the administrative header — followed by the NS records and the routing records (A, MX, CNAME, TXT), each governed by a TTL that controls caching.

As a term in the DNS vocabulary, the zone file is the container that ties the others together: nameservers hold and serve it, records are its contents, the SOA is its head, TTL governs caching, and propagation is the delay while a changed zone spreads. In practice you almost never touch the raw file — your host’s DNS editor presents the same records as a friendly table and writes your changes into the zone behind the scenes — but understanding the concept explains what that panel really does and why edits only count on your active nameservers. For a fuller beginner walkthrough, our dedicated DNS zone file guide goes deeper; as a terminology entry, the essential point is that a zone file is the authoritative file of all your domain’s DNS records, the single concept that makes the rest of the DNS vocabulary click into place.

When you are ready, you can start with Hostinger and use code PROTIPS for the reader discount. A zone file is the text file on your authoritative nameserver holding all of a domain’s DNS records (SOA first, then NS, A, MX, CNAME, TXT), the source of truth for where your site and email point. A ‘zone’ is the namespace a nameserver manages. You edit it through a friendly DNS panel, not raw text — and it’s the concept that ties nameservers, records, TTL, and propagation together.