Skip to main content
FR

DNS Zone Hosting

Primary or secondary authoritative DNS, with explicit plan limits and no DNS hostage tactics.

Get Started

At the last verified 2026-08-29 snapshot, production used the legacy platform; reverify the public state before relying on it. The catalogue, portal and API routes below describe the v2 launch code configuration; they are not evidence that these features are already available in production.

two ways to host

Primary, on us

At v2 launch, host your zone entirely on our nameservers. Manage records, DNSSEC and dynamic DNS through the portal or API, with no authoritative DNS server of your own to maintain.

Secondary, alongside yours

Keep your own primary while our secondaries retrieve the zone over AXFR/IXFR. TSIG authenticates the transfer and protects its integrity; it does not encrypt the contents. After a successful sync, our servers can keep answering if your primary becomes unavailable.

what is secondary dns?

Secondary DNS adds authoritative servers for your domain. Our secondaries retrieve a copy of the zone from the primary you control over AXFR or IXFR and serve it after a successful sync.

Redundancy

An already-synchronised copy can continue to be served if the primary becomes unavailable. The service uses three European locations.

Performance

Three locations provide multiple network paths. Actual latency and routing depend on the client, resolver and Internet path; the geographically nearest server is not guaranteed.

Compliance

The public fleet provides three nameservers. Check the delegation and diversity rules of your registry or registrar.

Pricing

v2 launch catalogue
  • Free — 2 managed authoritative zones + 5 secondary zones — €0
  • Hobby — 5 managed authoritative zones + 10 secondary zones — €2.39/month incl. tax (base €1.99/month before tax)
  • Pro — 15 managed authoritative zones + 30 secondary zones — €5.99/month incl. tax (base €4.99/month before tax)
  • Enterprise — unlimited managed authoritative and secondary zones — €35.99/month incl. tax (base €29.99/month before tax)

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.

Paid subscriptions recover the service's operating costs; they are not designed to generate profit.

Recurring payments 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.

After a failed payment, a seven-day grace period applies. At its end, the account returns to Free; existing DNS zones are not deleted, parked, redirected or monetised.

The Plesk pilot has a preview allocation from Pro, but remains unavailable without server-side enrollment and explicit installation admission.

Create Account

quick start

1. Create an account

Register at app.ledns.eu, then create an API key from your signed-in portal session if you want to automate setup.

2. Add your zone

Enter your domain and primary DNS server IP. Creation returns the TSIG name and secret before primary verification. Copy the secret: it authenticates transfers and protects their integrity, but does not encrypt them.

3. Configure your primary

Add the TSIG key to your primary DNS, allow our servers to retrieve the zone, and notify them when the zone changes.

4. Verify ownership

Add the TXT record shown by the portal, run verification, then confirm the first zone transfer succeeds before changing delegation.

configuration examples

Add this to your BIND configuration after receiving your TSIG key:

// /etc/bind/named.conf.local // 1. Define the TSIG key (shared secret for authentication) key "customer-xxxx.example.com" { algorithm hmac-sha256; secret "YOUR_TSIG_SECRET_HERE"; }; // 2. Configure your zone with transfer permissions zone "example.com" { type master; file "/etc/bind/zones/example.com.zone"; // Allow zone transfers only to clients with valid TSIG key allow-transfer { key "customer-xxxx.example.com"; }; // Notify our secondary NS servers when zone changes also-notify { 51.75.96.82; // ns-gra.ledns.eu 51.89.95.33; // ns-lim.ledns.eu 151.115.80.165; // ns-waw.ledns.eu }; };

For PowerDNS Authoritative Server:

# Add TSIG key pdnsutil import-tsig-key customer-xxxx.example.com hmac-sha256 'YOUR_TSIG_SECRET_HERE' # Set metadata for zone pdnsutil set-meta example.com TSIG-ALLOW-AXFR customer-xxxx.example.com pdnsutil set-meta example.com ALLOW-AXFR-FROM 51.75.96.82 51.89.95.33 151.115.80.165 pdnsutil set-meta example.com ALSO-NOTIFY 51.75.96.82 51.89.95.33 151.115.80.165

These routes match the v2 launch code and do not prove production availability. First create an API key from an authenticated portal session:

# Add a secondary zone with a placeholder API key curl -X POST https://control-xnqsyvgcprzaash17upkc5cd.DE-FRA-COG.ledns.infra.rqsco.cloud/api/v1/zones \ -H "Authorization: Bearer ldns_REPLACE_WITH_YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"domain": "example.com", "mode": "secondary", "primary_ip": "PRIMARY_DNS_IP"}' # Verify domain ownership curl -X POST https://control-xnqsyvgcprzaash17upkc5cd.DE-FRA-COG.ledns.infra.rqsco.cloud/api/v1/zones/example.com/verify \ -H "Authorization: Bearer ldns_REPLACE_WITH_YOUR_API_KEY"

our nameservers

After a successful first transfer, use the exact list shown in the portal at your registrar. The v2 launch fleet is configured as:

ns-gra.ledns.eu 51.75.96.82 (Gravelines, FR) ns-lim.ledns.eu 51.89.95.33 (Limburg, DE) ns-waw.ledns.eu 151.115.80.165 (Warsaw, PL)

In a standard hidden-primary setup, delegate the public nameservers and do not publish the hidden primary. If your design also publishes its primary, first validate that topology against the registry's requirements.