WAFGOPreparing your page
DNS cost planning

DNS costs: queries and routing policies

Prepare DNS requirements for zones, queries, records and policies, reviewing standard resolution, traffic steering, health checks and migration costs.

Overview

DNS queries are not the same as page views. When discussing resolution and delivery with WAFGO, include zone structure, caching periods, the existing provider and recovery requirements.

This is a DNS selection and cost-planning guide, not a claim of a launched authoritative-DNS service, free query allowance or traffic-steering package. Confirm service scope and charges separately.

01

Understand what drives query volume

Recursive resolver caching affects queries reaching authoritative servers, while TTLs, record changes and client behavior also influence the result. Base estimates on actual DNS measurements.

Zones and records

Inventory zones, subdomains and record types, including any zone- or record-count limits.

Query volume

Group query statistics by period and record type, checking how successful, failed and anomalous queries are counted.

TTL and changes

Set TTLs around freshness and reuse needs rather than sacrificing required recovery behavior just to reduce queries.

02

Separate resolution from additional policies

Geographical steering, health checks and failover may have separate billing units. A standard query rate does not imply every policy is included.

Separate resolution from additional policies
ScopeConfirm
Standard resolutionZone, domain, record and query billing units
Policy-based resolutionPolicy types, matching dimensions and additional query charges
Health checksTargets, frequency, probe regions and metering
Operations and supportChange support, record export, logs and migration
03

Include verification and recovery in migration

DNS migration needs a complete record inventory and a usable rollback plan. Mail, domain-verification and security-related records matter as much as website address records.

  • Export records and review mail, verification and critical subdomains before changes.
  • Confirm registrar access, relevant DNSSEC settings and responsibility for validation before and after switching.
  • Keep the previous configuration during transition and verify both DNS answers and real application access.

Implementation & checks

  1. 01

    Inventory DNS

    Export zones, records and current query statistics.

  2. 02

    Review policies

    List traffic-steering, health-check and recovery requirements.

  3. 03

    Confirm billing

    Agree on query measurement, add-ons and migration support.

Frequently asked questions

No. Caching, multiple asset hostnames and client behavior change query counts; use actual DNS measurements.

Not necessarily. Longer caching trades off against change propagation, so choose according to continuity requirements.

Start with your requirements

Make the architecture work for your business

Share your audience regions, content types and current challenges with WAFGO to clarify prerequisites, service scope and validation.

Discuss my requirements