What Is a DNS Zone?

A DNS zone is the part of a domain name space that is under the control of a single legal entity. The Domain Name System (DNS) translates human-readable domain names like www.amazon.com to a machine-readable IP address like 192.0.2.44. It defines a domain name space containing domains and subdomains (like .com, .org, etc.) that create naming consistency on the internet. A DNS zone is an administrative space that enables more precise control over DNS elements. It decentralizes the DNS, making it possible to manage on different levels. It also reduces the nameserver tasks by dividing responsibilities.

The DNS operates by using a distributed database system. This system involves several components, like resolvers, DNS zones, and authoritative DNS name servers. In the DNS hierarchy, there is one root domain at the top. This domain then branches into several second-level domains, individual hosts, and subdomains. When a user types a domain into their browser, a DNS resolver queries the DNS to find the server that holds that zone or domain.

DNS zones are vital in DNS infrastructure as they take responsibility for a small domain section. Each DNS zone contains domain records, like the IPv4 address, IPv6 address, canonical name, TXT, and mail exchange. When accessing specific domain pages, users access a DNS zone holding text-based records for that domain. A DNS zone allows users to efficiently manage and distribute information across several parts of an overall domain by holding all domain-related records.

DNS zones use a DNS zone file to construct connections between associated resources, IP addresses, and domain names.

DNS zone file

Each DNS zone file follows a strict structure outlined by DNS servers. It contains all the relevant resource records (RRs) for a domain. Each piece of information has a different function.

A DNS zone file holds the following information:

• The start of authority shares resource records about a zone, like its name server, refresh intervals, contact details, etc.

• The name server details the name of a server for the DNS zone.

• A and AAA records map domain names to their IPv4 and IPv6 addresses.

• Canonical names connect one domain to another through alias records.

• Mail exchange helps to identify the mail servers responsible for handling any email for the domain.

• TXT holds all of the text information that you associate with a domain.

You can automatically or manually update a DNS zone file. A dynamic DNS approach automatically updates all DNS records, which is useful when your IP addresses change frequently.

Several types of DNS zones fulfill different roles in DNS architecture. Each zone manages different areas in the DNS namespace.

Primary DNS zone

Primary zones contain all of the server’s DNS records. They hold a read/write copy of the zone data. Information in a primary zone is kept as a common.txt file. This format makes it easy to back up and recover DNS records.

When a DNS record updates, the changes log to the primary zone and replicate to the secondary zones. There is only one primary zone in a DNS server. As a primary zone acts as the central zone, it must be available if you want to make changes.

Secondary DNS zones

The secondary zone is a read-only copy of the primary DNS server, acting as a backup for the primary zone. By storing the same information, the secondary zone reduces the workload of the primary zone while also avoiding DNS architecture with a single point of failure. You cannot modify a DNS record in a secondary zone as it is read-only. It likely directs you to the primary zone if you attempt to do so.

Servers use zone transfers to increase fault tolerance in a DNS zone. Zone transfers synchronize data between primary and secondary DNS servers to maintain consistency across several zone servers. This strategy helps to ensure redundancy.

Active directory-integrated zone

An active directory-integrated zone stores DNS data in application directory partitions. This zone uses automatic replication to maintain a DNS zone without additional configuration. You store data as a container object in the active directory database.

Stub zone

A stub zone is a duplicate of another zone that only includes the most essential resources to identify the zone’s DNS servers. A stub zone is especially useful when resolving naming issues between different DNS namespaces. For example, when two companies merge, stub zones are useful for resolving naming issues.

Reverse DNS zone

In traditional DNS mapping, domain names map directly to an IP address. However, a reverse lookup DNS zone provides the opposite function. Reverse lookup zones allow you to search for domain names by reversing an IP address.

A reverse lookup zone serves the role of translating IP addresses into network resource names. For example, this approach aids email servers in verifying legitimate servers and blocking any messages that seem to come from an unreliable source. By comparing servers to PTR records, a reverse lookup zone allows email servers to determine the validity of the sender’s server.

A DNS zone and a DNS server are two DNS components that are commonly mistaken for one another. However, they are not the same and serve different roles in DNS architecture.

DNS zone vs. DNS server

A DNS zone is a small section of the wider DNS architecture. This architecture contains information about a large group of domain names and the records those domains hold. Every zone contains specific data for each domain, with a zone file containing addresses or server locations for that domain.

On the other hand, DNS servers represent the entire span of a DNS namespace. They contain all DNS zones and provide access to each zone. Servers manage and distribute information from a DNS zone in response to DNS queries. Overall, a server allows computers to connect to services and websites on the internet.

In short, DNS servers are the entire ecosystem, while a DNS zone represents a small fragment of the total architecture.

Amazon Route 53 provides highly available and scalable Domain Name Systems (DNS), domain name registrations, and health-checking web services. Route 53 is an “authoritative DNS” system that provides an update mechanism developers use to manage their public DNS names. It then answers DNS queries, translating domain names into an IP address so computers can communicate with each other. You can combine your DNS with health-checking services to route traffic to healthy endpoints or to monitor endpoints independently.

Amazon Lightsail is a virtual private server provider with computing, storage, and networking capacity and capabilities. It is used to deploy and manage websites and web applications in the cloud. Lightsail includes everything you need to launch your project quickly—virtual machines, containers, databases, CDN, load balancers, DNS management, and more—for a low, predictable monthly price.

You can manage the DNS records of your domain using the registrar where you registered your domain, or you can manage them using Lightsail. If you transfer your domain’s DNS records to Lightsail, you can efficiently administer your domain and compute resources together in one place.

You manage the DNS records by creating a Lightsail DNS zone. You can create up to six Lightsail DNS zones. If you require more, we recommend using Amazon Route 53 to manage all your domains’ DNS. You can use Route 53 to route traffic for your domain to your Lightsail resources.

Start managing a DNS zone on AWS by creating an account today.