Understanding DNS Query Usage
Learn how to monitor your DNS query usage, understand excess volume charges, and access your billing history in DNScale.
Answer snapshot
DNScale meters DNS queries per zone and aggregates them into your monthly usage total. The dashboard's Usage tab shows current-period query count, breakdown by record type, and response-code distribution (NOERROR, NXDOMAIN, REFUSED). Excess queries beyond your plan allowance bill at a per-million rate; PAYG bills every query. To reduce query cost, raise TTLs on stable records — longer caching means fewer hits to authoritative nameservers.
What you'll learn
- Navigate the DNScale usage dashboard to monitor current and historical DNS query volume
- Understand how excess volume billing works and calculate estimated charges based on plan tiers
- Analyze query type breakdowns and response code distributions to optimize zone health
- Use TTL tuning and plan selection to manage query costs effectively
DNScale tracks your DNS query usage to help you understand your traffic patterns and manage your subscription effectively. This guide explains how to view your current and historical usage, understand excess volume charges, and optimise your plan.
Accessing Usage Information
Your DNS usage information is available in the dashboard under the Usage tab. To access it:
- Log in to your DNScale dashboard
- Click on the Usage tab in the main navigation
- View your current month's usage summary and historical data
Usage Summary Card
The Usage Summary card displays your current billing period at a glance:
Key Metrics
- Total Queries -- The number of DNS queries received across all your zones this billing period
- Included Queries -- The query allowance included in your plan
- Usage Percentage -- How much of your included allowance you've used
- Remaining -- How many queries you have left before incurring excess volume charges
Status Indicators
The usage summary includes a status badge:
- Normal -- Usage below 75% of your included queries
- High Usage -- Usage between 75-90% of your included queries
- Near Limit -- Usage between 90-100% of your included queries
- Over Limit -- Usage exceeds your included queries (excess volume charges apply)
Excess Volume Explained
When your DNS query usage exceeds your plan's included allowance, you'll be charged for the additional queries at your plan's excess volume rate.
Excess Volume Rates by Plan
| Plan | Included Queries | Excess Volume Rate |
|---|---|---|
| Nano | 5 million/month | €0.20 per million |
| Pro | 25 million/month | €0.10 per million |
| Scale | 250 million/month | €0.10 per million |
Note: The Nano Free tier does not include excess volume billing. If you exceed your 1 million query limit, consider upgrading to a paid plan.
How Excess Volume is Calculated
Excess volume charges are calculated at the end of each billing period:
- Total queries for the month are summed across all zones
- Included queries are subtracted from the total
- Remaining queries (if positive) are the excess volume
- Excess volume is multiplied by your plan's per-million rate
Example: If you're on the Nano plan and use 7.5 million queries:
- Included: 5 million
- Excess volume: 2.5 million
- Charge: 2.5 x €0.20 = €0.50
Excess Volume Alert
When excess volume is detected, an alert appears in your Usage Summary:
Excess Volume Detected You have used X queries above your included limit. Estimated excess volume charge: €X.XX
This helps you anticipate your bill before the end of the billing period.
What Counts as a Query?
Every DNS query that reaches DNScale's authoritative nameservers counts toward your usage. This includes:
- Successful lookups (NOERROR) for any record type -- A, AAAA, MX, TXT, etc.
- Non-existent domain responses (NXDOMAIN) -- queries for subdomains that don't have records
- DNSSEC-related queries -- DNSKEY, DS, and RRSIG lookups triggered by DNSSEC validation
- Health check queries -- monitoring systems that periodically query your records
Queries answered from resolver caches do not count. This is why TTL settings directly impact your query volume -- longer TTLs mean more cache hits and fewer queries reaching your authoritative servers.
A single page load can generate multiple DNS queries: one for the A record, one for the AAAA record, one for the HTTPS record, and potentially more for subdomains used by CDNs or APIs. Understanding this multiplier helps you forecast usage accurately.
Query Trends Chart
The Query Trends chart shows your daily query volume over time. Use this to:
- Identify traffic patterns and peak usage days
- Spot unusual spikes that might indicate DNS attacks or misconfigurations
- Plan capacity based on growth trends
You can hover over any day to see the exact query count.
Query Type Breakdown
The Query Types chart shows the distribution of DNS record types being queried:
| Query Type | Description | Typical Share |
|---|---|---|
| A | IPv4 address lookups | 40-60% |
| AAAA | IPv6 address lookups | 15-30% |
| CNAME | Canonical name lookups | 2-5% |
| MX | Mail server lookups | 1-5% |
| TXT | Text record lookups (SPF, DKIM, etc.) | 5-15% |
| NS | Nameserver lookups | 1-3% |
| HTTPS | Service binding lookups | 1-5% |
| Other | Less common record types | Variable |
This helps you understand what types of DNS queries your domains receive. A surge in TXT queries might indicate increased email verification lookups, while an unexpected spike in AAAA queries could reflect growing IPv6 adoption among your users.
Response Code Distribution
The Response Codes chart shows the outcome of DNS queries:
- NOERROR -- Successful queries with valid responses
- NXDOMAIN -- Queries for non-existent domains/records
- SERVFAIL -- Server failures (should be minimal)
- REFUSED -- Refused queries (policy-based rejections)
A healthy zone should have mostly NOERROR responses. High NXDOMAIN rates might indicate misconfigured clients, outdated references, or an NXDOMAIN attack. Elevated SERVFAIL rates could signal DNSSEC validation issues.
Usage by Zone
The Usage by Zone breakdown shows which zones consume the most queries. This helps you:
- Identify high-traffic zones that might need optimisation
- Understand traffic distribution across your domains
- Make informed decisions about zone-level caching or TTL settings
Billing History
The Billing History table shows your monthly usage and charges:
| Column | Description |
|---|---|
| Period | The billing month (e.g., "November 2024") |
| Total Queries | Total queries for that month |
| Included | Queries included in your plan |
| Excess Volume | Queries above your included limit |
| Charges | Excess volume charges for that month |
| Status | "Within Limit" or "Excess Volume" |
Viewing Past Months
By default, the last 12 months of billing history are displayed. Use the pagination to view older records if needed.
Pro-Rated Billing
If you signed up or changed plans mid-month, your usage may be pro-rated:
- Days Active -- Days your account was active during the billing period
- Days in Month -- Total days in the billing month
- Included Queries -- Adjusted proportionally based on active days
For example, if you sign up on the 15th of a 30-day month on the Nano plan:
- Standard monthly allowance: 5 million queries
- Pro-rated allowance: 2.5 million queries (15/30 x 5M)
API Access to Usage Data
You can also retrieve usage data programmatically via the DNScale API:
Current Month Usage
GET /v1/usage/currentUsage Summary for Specific Month
GET /v1/usage/summary?month=2024-11Daily Usage Statistics
GET /v1/usage/daily?start_date=2024-11-01&end_date=2024-11-30Zone-Specific Usage
GET /v1/zones/{zone_id}/usage?start_date=2024-11-01&end_date=2024-11-30Billing History
GET /v1/billing/history?limit=12For API access, create an API key with the usage:read and billing:read scopes. You can also integrate this data into infrastructure-as-code workflows using the Terraform provider or DNSControl.
Tips for Managing Usage
Optimise TTL Values
Higher TTL values reduce the number of queries by allowing clients to cache responses longer. See our TTL best practices guide for recommended values:
| Record Stability | Recommended TTL | Impact on Queries |
|---|---|---|
| Highly stable (MX, TXT, NS) | 86400 (24h) | Minimal query volume |
| Stable (A, AAAA for static sites) | 3600 (1h) | Low query volume |
| Moderate (A records that may change) | 900 (15m) | Moderate query volume |
| Dynamic (failover endpoints) | 300 (5m) | Higher query volume |
Monitor Traffic Patterns
Regular monitoring helps you:
- Identify unexpected traffic spikes early
- Detect potential abuse or attacks
- Plan for capacity needs before hitting limits
Choose the Right Plan
If you consistently hit your query limits, consider upgrading. See our plans comparison for details:
- Nano to Pro: 5x more queries at a lower excess volume rate
- Pro to Scale: 10x more queries for high-traffic needs
It's often more cost-effective to upgrade than pay consistent excess volume charges.
Need Help?
If you have questions about your usage or billing:
- Check the Support page for contact options
- Review your usage trends in the dashboard
- Learn how to update your payment method if needed
- Consider upgrading if you're consistently near your limits
Conclusion
Understanding your DNS query usage helps you manage costs and keep DNS resolution healthy for your domains. The DNScale dashboard shows current and historical usage so you can tune TTLs, spot unusual traffic, and compare your usage with the current plan options.
Frequently asked questions
- How can I reduce my DNS query bill?
- The single highest-leverage change is raising TTLs on stable records. A record with TTL 300 is queried roughly 12× more often than the same record with TTL 3600, because resolver caches refresh more often. For records that don't change frequently (apex A, MX, TXT for SPF), 3600–86400 TTL is appropriate and dramatically lowers query volume.
- What query types make up my volume?
- For most zones, A and AAAA queries dominate (web traffic). Email-heavy domains see significant MX, TXT (SPF), and DNSKEY queries (DNSSEC). DNScale's Usage panel breaks down query volume by record type so you can spot which traffic is driving cost — e.g., abnormally high TXT queries often mean a misconfigured SPF flattener.
- Why are NXDOMAIN responses counted as queries?
- Because they require a full lookup at the authoritative nameserver — same cost as a NOERROR response. High NXDOMAIN counts often signal misconfigured external systems probing names that don't exist; investigate the source and stop the probes if you can. NXDOMAIN floods can also be a DDoS pattern (water-torture attacks).
- Is the usage data real-time or delayed?
- Near-real-time — the dashboard reflects query activity within a few minutes. The exact final invoice number is computed at month-end after deduplication and aggregation across all PoPs. For estimating mid-month, the dashboard's projected total is reliable to within a few percent.
- Can I get usage data via the API?
- Yes — the DNScale REST API exposes query usage per zone, with daily resolution and breakdown by record type and response code. Useful for piping into your own dashboards or building cost-allocation reports across multiple zones for chargeback.
Related guides
Platform
How to Close Your Account
Learn how to permanently close your DNScale account, what happens to your data, and how to resolve outstanding invoices before closing.
Platform
How to Update Your Payment Method
Learn how to update your credit card, change your default payment method, or update billing information on your DNScale account.
Platform
Multi-User Accounts and Zone Access Control
Learn how to invite team members to your DNScale account, assign roles, and control which DNS zones each user can access.
Platform
Paid Plans vs Pay As You Go
Understand the differences between DNScale's subscription plans and Pay As You Go pricing, and find out which option suits your needs best.
Ready to manage your DNS with confidence?
DNScale provides anycast DNS hosting with a global network, real-time analytics, and an easy-to-use API.
Start free