DNS Record Limits and Overage Fees
Last updated
Each DNS zone has a record limit set by your plan. A zone on Solo Pro or Teams can grow above its limit, and the records above the limit cost $1.00 each month for each block of 500. On Solo, a zone cannot go above its limit. On Enterprise, the limit is set in your contract. The table below gives the policy of each plan.
Table of Contents
- Record limits and overage by plan
- How the overage is calculated
- Stopping new records above the limit
- Seeing how many records a zone has
- Have more questions?
Record limits and overage by plan
| Plan | Records per zone | Above the limit |
|---|---|---|
| Solo | 100 | You cannot add records above the limit |
| Solo Pro | 500 | $1.00 per month for each block of 500 records above the limit, or no records above it if your account chose |
| Teams | 1,000 | $1.00 per month for each block of 500 records above the limit, or no records above it if your account chose |
| Enterprise | Set in your contract | Contact us |
The legacy Personal plan has the Solo limit, and the legacy Professional and Business plans have the Teams limit and overage.
Every record counts toward the limit, including system records, however the record was added. To compare the other features of each plan, see DNSimple Plans.
How the overage is calculated
Records above the zone’s limit are billed in blocks of 500, and a partial block counts as a full block. Each block costs $1.00 per month. On a legacy plan billed yearly, each block costs $12.00 per year.
On the Teams plan, with a limit of 1,000 records:
- 1,000 records is $0.00, because the zone is at its limit
- 1,001 records is $1.00, because 1 record above the limit counts as one block
- 1,500 records is $1.00, because 500 records above the limit is one block
- 1,501 records is $2.00, because 501 records above the limit counts as two blocks
On the Solo Pro plan, with a limit of 500 records, a zone with 1,200 records is $2.00, because 700 records above the limit counts as two blocks.
Each zone is calculated on its own. Only active primary zones have an overage charge. Secondary zones and inactive zones do not.
The overage is a separate line on your invoice.
Stopping new records above the limit
On a plan with the overage, an account administrator can choose . Zones in an account with this setting cannot grow above their limit. When a zone reaches its limit, you can still update and delete its records, but you cannot add records until you delete some, or upgrade your plan if a plan with a higher limit is available.
To block new records above the limit
- Select the relevant account from the account switcher, then click the gear icon next to the account name to open .
- Click the tab.
- In the card, click .
- Select , then click .
To allow records above the limit again, follow the same steps and select .
Seeing how many records a zone has
The Record Editor shows how many records the zone has out of its limit, and warns you when the zone is close to it.
If you manage your zones through the API, retrieving a zone returns records_count, the number of records in the zone, and records_limit, the zone’s limit. The API returns these fields only when you retrieve a single zone, not when you list zones.
Have more questions?
If you have any questions about your record limits or how we calculate the overage, contact us, and we’ll be happy to help. You can also read more about DNSimple pricing.