Network

Review an Example Zone and Verify Its Apex Records

·

Use a zone review to confirm which owner and TTL each record receives. Then confirm the proposed serial change and check what the complete file needs before deployment.

DNS Zone File Validator

Confirm the apex and read the new SOA serial

Choose Load example. Enter 2026112100 in Previous SOA serial and choose Validate BIND zone. You should see nine parsed records, zero errors, and a serial advance to 2026112101.

Read the SOA and NS rows at example.test. The indented NS record inherits the owner of the previous SOA. The default $TTL of 1h appears as 3600 seconds, while each www address uses its own 5m TTL of 300 seconds. The relative owner www becomes www.example.test.

Open DNS Zone File ValidatorBIND 9 zone file documentationRFC 1982 DNS serial number arithmetic

Check a missing nameserver and a wrapping serial

Remove the indented IN NS ns1 line from the example and validate again. The report calls for at least one apex NS record. Keep the address record for ns1 in the example and observe that it describes the host's address.

For a second exercise, restore the example and set its SOA serial to 0 and the previous value to 4294967295. The report shows an advance under the serial arithmetic in RFC 1982. A difference of exactly half the 32-bit range is ambiguous.

Open DNS Zone File ValidatorRFC 1982 DNS serial number arithmeticRFC 1035 DNS master file syntax

Check the review scope before exporting

Use a $ORIGIN or set Zone origin when you have relative names. A final dot makes a name absolute. The workspace preserves indented owners, comments, and records continued inside parentheses.

Expand $INCLUDE and $GENERATE in your own zone workflow, and review any unsupported type separately. Download the JSON report and keep it with the exact source file. Use your deployment's complete validator and configuration when the zone includes additional features.

Open DNS Zone File ValidatorBIND 9 zone file documentationRFC 1035 DNS master file syntax

Common questions

Will changing the SOA serial here publish a zone transfer?

The browser compares the numbers you provide. Publication and secondary transfer come from your deployed DNS configuration.

Where does a record get its TTL?

The report uses the explicit TTL first, then the active $TTL directive. It labels an unavailable TTL as unspecified.

Sources

Put it into practice.

Related guides