Skip to content
Calcrivo

DNS Zone Size Calculator

Estimate zone file size, server memory and zone transfer time from your record counts and DNSSEC state.

Inputs

records
records
records
records
bytes
Mbit/s

Total Records

9,600

Zone File Size

1 MiB

Server Memory Footprint

4 MiB

Zone Transfer Size

3 MiB

Zone Transfer Time

0.230s

Step by step

  1. Values used

    A records = 5,000 records; AAAA records = 3,000 records; CNAME records = 1,200 records; MX, TXT, SRV and other records = 400 records; Average bytes per zone-file line = 120 bytes; Zone is DNSSEC signed = Yes; Transfer bandwidth = 100 Mbit/s

  2. DNS Zone Size

    zone bytes = total records × average bytes per record, plus roughly 180 bytes per record of RRSIG when DNSSEC is signed.

  3. AXFR transfer time

    transfer time = zone transfer bytes × 8 ÷ bandwidth

  4. Total Records

    = 9,600

  5. Zone File Size

    = 1,152,000

  6. Server Memory Footprint

    = 4,128,000

  7. Zone Transfer Size

    = 2,880,000

  8. Zone Transfer Time

    = 0.230 s

How it works

Zone file size is simply the record count times the average line length, while in-memory representation costs more per record because of indexes and pointers. DNSSEC roughly doubles a zone because every RRset gains a signature, and the NSEC or NSEC3 chain adds records of its own. Large signed zones dominate secondary start-up time and AXFR bandwidth, and a zone that no longer fits in memory turns every query into a disk read.

Formulas

DNS Zone Size

zone bytes = total records × average bytes per record, plus roughly 180 bytes per record of RRSIG when DNSSEC is signed.

total records
Sum of every RR type in the zone
RRSIG
Signature record added per RRset by DNSSEC
180 bytes
Typical RSA/ECDSA signature plus owner name overhead

AXFR transfer time

transfer time = zone transfer bytes × 8 ÷ bandwidth

bandwidth
Link rate between primary and secondary, in bits/s

Frequently Asked Questions

How is DNS Zone Size calculated?

zone bytes = total records × average bytes per record, plus roughly 180 bytes per record of RRSIG when DNSSEC is signed. Zone file size is simply the record count times the average line length, while in-memory representation costs more per record because of indexes and pointers. DNSSEC roughly doubles a zone because every RRset gains a signature, and the NSEC or NSEC3 chain adds records of its own.

Why does DNS Zone Size matter?

Large signed zones dominate secondary start-up time and AXFR bandwidth, and a zone that no longer fits in memory turns every query into a disk read.

What values do I need to enter?

This calculator takes 7 inputs: A records, AAAA records, CNAME records, MX, TXT, SRV and other records, Average bytes per zone-file line, Zone is DNSSEC signed, Transfer bandwidth. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

You might also need