How to configure custom DNS settings on NordVPN
Configure custom DNS settings in NordVPN by accessing the app settings, navigating to the DNS section, and entering your preferred DNS server addresses. Custom DNS can be used alongside NordVPN's CyberSec feature or as a replacement for improved privacy and performance.
Prerequisites
- Active NordVPN subscription
- NordVPN app installed on your device
- Administrative access to your device
- Knowledge of preferred DNS server addresses
Step-by-Step Instructions
Open NordVPN Application
Access Settings Menu
Navigate to DNS Settings
Enable Custom DNS
Enter Primary DNS Server
- Cloudflare:
1.1.1.1 - Google:
8.8.8.8 - Quad9:
9.9.9.9 - OpenDNS:
208.67.222.222
Configure Secondary DNS Server
- Cloudflare:
1.0.0.1 - Google:
8.8.4.4 - Quad9:
149.112.112.112 - OpenDNS:
208.67.220.220
Save and Apply Settings
Verify DNS Configuration
dnsleaktest.com or whatsmydnsserver.com to verify your custom DNS servers are being used. The test should show your configured DNS addresses instead of NordVPN's default DNS servers.Common Issues & Troubleshooting
Custom DNS settings not saving or appearing grayed out
Ensure you have the latest version of NordVPN app installed. Restart the application and try again. On some platforms, you may need to disable CyberSec feature first before enabling custom DNS.
DNS leak test shows NordVPN's DNS instead of custom DNS
Disconnect from the VPN server completely, wait 30 seconds, then reconnect. Clear your browser's DNS cache by typing chrome://net-internals/#dns in Chrome and clicking Clear host cache.
Internet connection becomes slow or unstable after changing DNS
Try different DNS servers as some may have better performance in your location. Test with 1.1.1.1 and 1.0.0.1 (Cloudflare) which are generally fast and reliable worldwide.
Cannot access certain websites after configuring custom DNS
Some DNS providers block certain content categories. Switch to a different DNS provider like Google DNS (8.8.8.8, 8.8.4.4) or disable custom DNS temporarily to test if DNS filtering is the cause.