Configure le_dns on Your Router
Protect every device on your network at once
Changing DNS on your router is the most powerful option: every device on your network — phones, laptops, smart TVs, IoT gadgets, guest devices — automatically uses le_dns without any per-device configuration.
Before you start
You need access to your router’s admin interface. Typically:
- Open a browser and go to
http://192.168.1.1orhttp://192.168.0.1 - Log in with your admin credentials (often printed on the router’s label)
Generic steps (applies to most routers)
- Log into your router admin panel
- Find DNS settings — usually under one of:
- WAN / Internet settings
- DHCP settings (for distributing DNS to local devices)
- Advanced → DNS
- Replace the existing DNS addresses with:
- Primary DNS:
51.75.96.82 - Secondary DNS:
51.89.95.33 - Tertiary DNS (if supported):
151.115.80.165
- Primary DNS:
- Save and apply
Fritz!Box
- Open Internet → Account Information → DNS rebind protection (optional, can stay enabled)
- Go to Internet → DNS
- Select Use other DNSv4 servers
- Set Preferred DNSv4 server:
51.75.96.82 - Set Alternative DNSv4 server:
51.89.95.33 - Click Apply
Livebox (Orange)
- Go to Configuration avancée → Réseau → DNS
- Replace the ISP DNS entries with:
51.75.96.8251.89.95.33
- Save
Other ISP boxes (SFR, Bouygues, Freebox)
Freebox: Freebox OS → Paramètres de la Freebox → DHCP → DNS
Most ISP boxes have DNS settings under:
- Advanced settings → DNS
- DHCP configuration → DNS servers
- Network → LAN → DNS
A note on encryption
Router-level DNS changes DNS to le_dns, which prevents your ISP from intercepting your queries. However, the connection from your router to le_dns is plain DNS (UDP/TCP port 53) — not encrypted in transit.
For end-to-end encryption, configure DoH or DoT on each device individually. See the DoH setup guide or use the Private DNS setting on Android or a DNS profile on iOS.
Verify it works
From any device on the network, visit dnsleaktest.com. The DNS servers listed should be le_dns. If your ISP’s servers still appear, check that DHCP is distributing the new DNS (you may need to reconnect devices or flush their local DNS cache).