Create and Validate DNS Zone Files
The domain name for this zone (ORIGIN)
Default time-to-live in seconds
SOA Record Settings
Use "." instead of "@" (admin.example.com)
YYYYMMDDNN format (auto-generated)
Secondary refresh interval (seconds)
Retry interval after failure (seconds)
Zone expiration time (seconds)
Minimum TTL for negative responses
DNS Records
No records added yet. Click "Add Record" to begin.
Common Questions
What is a DNS Zone File?
A DNS zone file is a text file that defines a DNS zone by containing all the records for every domain within that zone. It maps domain names to IP addresses and other domain-specific information, essentially functioning as a critical configuration file that tells DNS servers how to route traffic for a domain.
What's the difference between common DNS record types?
Different record types serve specific purposes: A records map domain names to IPv4 addresses, AAAA records map to IPv6 addresses, CNAME records create aliases pointing to other domains, MX records specify mail servers, TXT records store text information for various purposes like verification, NS records identify authoritative name servers, and SRV records define the location of specific services.
What is an SOA record and why is it important?
The Start of Authority (SOA) record is mandatory in every zone file. It identifies the primary DNS server authoritative for the zone, contains administrator contact information, and includes critical parameters like serial number (for version control), refresh rate, retry interval, expiration time, and minimum TTL. These parameters control how DNS data is updated and maintained across the network.
What does the '@' symbol mean in a zone file?
The '@' symbol is a special notation that represents the zone's origin (root domain) as defined in the $ORIGIN directive. Using '@' as the name field in a record is equivalent to using the fully qualified domain name of the zone. For example, in a zone file for example.com, '@' would represent 'example.com.' itself.
Why do some domain names end with a period in zone files?
A trailing period (dot) at the end of a domain name indicates an absolute or fully qualified domain name, telling the DNS server not to append the zone origin. Without the trailing period, the zone's origin is automatically appended to the domain name. For example, 'www' might become 'www.example.com', while 'www.' would remain as-is.
How do I update my zone file once it's deployed?
When making changes to a zone file, always increment the serial number in the SOA record to ensure the changes propagate to secondary DNS servers. After editing, validate the syntax using tools like 'named-checkzone', then reload your DNS server configuration. Remember that DNS changes can take time to propagate globally, depending on TTL settings.