I was about to write a completely different article. The plan was simple: set a custom DNS on NordVPN, load a site, take a screenshot, prove it works, move on. Instead I caught myself making the exact mistake that probably explains half the “NordVPN custom DNS not working” complaints out there. I didn’t notice it in the moment. I only saw it going back through my own screenshots afterward.
That’s the article now. Not “here’s a clean test,” but “here’s what actually happens when you think you’re testing something and you’re not.”
Setting the custom DNS
Custom DNS on, 1.1.1.1 entered and saved, checkmark next to “Use custom DNS.” Normal so far. Except look at the bottom of that screenshot — there’s a small gray banner that says “VPN connection resumes in 14:16” with a pause icon next to it. I’d paused the connection earlier for something unrelated, forgotten about it, and gone straight into DNS settings without reconnecting first.
I didn’t catch that at the time. I want to be honest about that instead of pretending I planned this.
Testing a site while I thought the DNS was active
Forbes loaded completely. Articles, images, an ad, a newsletter box, a video thumbnail for a breaking story — the whole page, no errors, nothing missing. In the moment, that looked like exactly what I expected: custom DNS set, site loads fine, test passed, done.
Except the VPN wasn’t actually connected while any of that happened. It was paused. Which means none of it went through NordVPN at all — not the tunnel, and definitely not the custom DNS setting sitting one screen away. I was testing my phone’s regular internet connection and mistaking it for a successful VPN test.
Where I actually noticed
Going back to the main screen a minute later, there it was — Miami, red icon, “Not secured,” a button asking me to reconnect. That’s the moment the mistake became obvious. The custom DNS setting I’d configured had never actually been in use for that Forbes test. It couldn’t have been. There was no tunnel for it to run through.
This is, I think, exactly the trap behind a lot of “NordVPN custom DNS not working” reports. The setting itself can be sitting there, saved and correct, while the connection carrying it is paused, disconnected, or reconnecting in the background — and a site loading normally during that window looks identical to a successful test. Nothing on screen tells you which one actually happened unless you go check.
What I did next: tried to break it on purpose
Once I’d reconnected properly, I wanted to see what NordVPN actually does when you feed it a broken DNS entry instead of a working one — since that’s the other common story behind this complaint, a typo that fails silently and quietly wrecks the connection.
I typed “1.1.1” instead of “1.1.1.1” — one digit short of a working address — and hit Add. NordVPN didn’t accept it quietly. A red outline appeared around the field immediately, along with “DNS server not found,” and the Add button sat there waiting instead of saving anything. No silent failure, no confusing behavior afterward. It just refused the bad entry outrights
NordVPN Custom DNS Not Working That matters, because it rules out one of the more common explanations people reach for. If your custom DNS genuinely isn’t working, a straightforward typo in the address is less likely to be the reason than you’d think — the app is actively checking the format before it lets you save it.
NordVPN Custom DNS Not Working: What I Actually Found
Not a bug. Not something broken inside NordVPN’s DNS handling. In my case, it was a paused connection sitting quietly in the background while I tested something that never touched it. That’s an easy mistake to make precisely because nothing about a normally loading webpage tells you whether your VPN was actually carrying that traffic or not.
NordVPN Custom DNS Not Working If you’ve set a custom DNS and things feel inconsistent — working sometimes, not others, no clear pattern — the very first thing worth checking isn’t the DNS address at all. It’s whether the connection was actually active the entire time you were testing it.
How to actually check this yourself
- Open the NordVPN app before testing anything and confirm the main screen says “Secured,” not “Not secured” or “Paused”
- Go into DNS settings and confirm Custom DNS is checked and your address is listed under “Added DNS servers”
- Load a site and take note of the exact time
- Immediately after, go back to the main screen and confirm it still says Secured — not paused, not reconnecting
- If you want to test a genuinely broken entry, try removing a character from a known address like 1.1.1.1 and watch whether the app accepts or rejects it
Quick answers
Is NordVPN’s custom DNS actually broken?
Not based on this. The setting itself worked as expected once the connection was actually active — the failure in my case was an unnoticed paused connection, not the DNS feature itself.
Does a typo in the DNS address cause silent failures?
Not in this test. Entering an incomplete address triggered an immediate, visible error and the app refused to save it — no silent breakage, no confusing aftermath.
How would I know if my connection is paused without checking manually?
Right now, you mostly wouldn’t, unless you look at the main screen. A page loading normally gives no indication either way — that’s exactly what made this mistake easy to miss in the moment.
Why does this matter more than it sounds like it should?
Because it changes where you should actually look first. A DNS setting that’s correctly configured but sitting behind a paused or disconnected VPN will produce exactly the same symptoms as a genuinely broken DNS setting — inconsistent results with no obvious cause.
Related: see our NordVPN DNS settings not working test, NordVPN DNS servers not working test, and NordVPN DNS leak test for the rest of this series.
