Choosing a DNS Provider

Compare evidence, not slogans

Two different products

A public recursive resolver answers DNS questions for your devices. An authoritative DNS provider serves records for domains you control. They have different security, privacy and availability requirements, so comparing them in one unchecked feature table is misleading.

le_dns provides:

• a public resolver without voluntary advertising, family or commercial filtering, using classic DNS, DoH, DoT and DoQ; and
• primary and secondary authoritative DNS with four cost-recovery plans for the v2 launch.

le_dns catalogue

France consumer reference (75001), in EUR, without a discount or business tax exemption. The final total depends on buyer details confirmed by Paddle before payment. Estimate for your country. Live checkout is not open during qualification.

* Only authoritative and secondary zone counts are unlimited. Enterprise records, queries, API rate, history, teams, members and health checks retain the finite fair-use, safety or admission maxima published on the pricing page.

Stable means a v2 launch contract after verified cutover. Preview allocation means the feature is unavailable until server-side enrollment is deployed, its external acceptance gate passes and the account or Plesk installation is explicitly enrolled; buying Pro or Enterprise does not activate it. Smart/active authoritative answers are unavailable on every plan.

Monthly subscriptions are being qualified with Paddle as reseller; live checkout is not open. Paddle collects applicable taxes and shows the final tax-inclusive total before payment. Subscriptions fund infrastructure. Neither query data nor DNS-answer redirection funds the service. Existing DNS data is never redirected to advertisements or parking pages because of billing state.

When le_dns may fit

• You want an independent European operator and a fleet published in the European Union.
• You need primary or secondary DNS, DDNS and DNSSEC from the same operator.
• You value an AGPLv3 implementation and documentation that separates repository implementation from production and independent verification.
• You accept a best-effort service without a contractual SLA or worldwide Anycast claim.

When to look elsewhere

• For integrated threat blocking, choose a resolver that explicitly publishes and maintains that policy.
• For global Anycast and hundreds of points of presence, a global operator will generally fit better.
• For a specific authoritative product, compare complete authoritative offerings rather than resolver addresses.
• For a generally available hosting-panel integration today, wait until the Plesk pilot and server-side enrollment gates are complete or choose an already deployed integration.

Privacy questions that matter

“No logs” is insufficient. Ask every provider:

• whether a complete source address reaches persistent storage;
• whether individual address-to-domain events remain;
• which dimensions are aggregated and after which threshold;
• how long aggregates, audits and technical logs remain; and
• which processors and international transfers are actually involved.

The le_dns answer is documented in the privacy policy. The v2 analytics design describes thresholded domain/network aggregates, not a claim that no data exists, and must not be presented as the deployed legacy telemetry path before cutover.

External comparisons

Provider protocols, prices, logging policies and jurisdictions change. le_dns does not publish an undated binary yes/no matrix about competitors. Verify current facts in each provider’s primary documentation and record the product scope and date checked.

Next

• Pricing and billing
• Organization features
• Resolver setup guides