Secondary DNS Hosting

what is secondary dns?

Secondary DNS provides redundancy for your domain's DNS. Your primary server (the one you control) pushes zone updates to our secondary servers via AXFR/IXFR transfers. If your primary goes down, our secondaries keep serving your DNS records.

Redundancy

Your domains stay online even if your primary DNS fails. We serve from multiple European locations.

Performance

Geographic distribution reduces latency. Queries are answered by the nearest server.

Compliance

Many registrars require at least 2 nameservers. We provide the second one.

pricing

Free Tier

0 EUR

forever

Up to 5 zones
Automatic zone transfers (AXFR/IXFR)
Per-zone TSIG authentication
Domain ownership verification
REST API + Web UI
Multi-server redundancy (gra + lim)

Create Account

quick start

1. Create an account

2. Add your zone

Enter your domain and primary DNS server IP. We'll generate a unique TSIG key for secure transfers.

3. Configure your primary

Add the TSIG key to your primary DNS and allow zone transfers to our servers.

4. Verify ownership

Add a TXT record to prove you own the domain, then we'll start syncing your zone.

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.83.90.178; // ns1.ledns.eu (gra secondary IP) 51.89.103.206; // ns2.ledns.eu (lim secondary IP) }; };

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 pdnsutil set-meta example.com ALSO-NOTIFY 51.75.96.82,51.89.95.33

Use the REST API for automation:

# Register and get API key curl -X POST https://ledns.eu/api/v1/register \ -H "Content-Type: application/json" \ -d '{"email": "you@example.com"}' # Add a zone curl -X POST https://ledns.eu/api/v1/zones \ -H "Authorization: Bearer ldns_YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"domain": "example.com", "primary_ip": "YOUR_PRIMARY_IP"}' # Verify domain ownership curl -X POST https://ledns.eu/api/v1/zones/example.com/verify \ -H "Authorization: Bearer ldns_YOUR_API_KEY"

our nameservers

After your first successful zone transfer, add these NS records at your registrar:

ns1.ledns.eu 51.83.90.178 (Gravelines, FR) ns2.ledns.eu 51.89.103.206 (Limburg, DE)

Keep your primary nameserver as NS1, add ours as NS2/NS3.