NordVPN Linux bug blocks browsing despite active connection
The client can report a successful connection while domain lookups fail.
That points to name resolution rather than a complete VPN connection failure. The computer cannot resolve domain names, leaving browsers and domain pings unable to reach their destinations.
NordVPN describes Linux 6.0 as a major release and advises users to review scripts and configurations because commands and the interface are changing.
What Linux users are experiencing
Reports on Reddit and GitHub describe "server not found" errors. Users on Linux Mint and Ubuntu have reported them. Arch users have too. One user summed up the contrast: "If I disconnect from Nord, the internet works fine. When I connect, it doesn't." NordVPN's team has acknowledged a problem with its Linux application. Developers are preparing a permanent fix for the upcoming 6.0.0 release.
A Reddit user also reported seeing a notice on NordVPN's official website. The article's publisher said it could not find that notice, even when checking from a Linux machine, so it could not independently confirm the report. Separately, NordVPN's Linux 6.0 migration guidance, published October 6 and updated October 11, discusses changed commands and interface migration. It does not say the DNSSEC issue has been fixed in version 6.0.0.
A Microsoft WSL issue report describes NordLynx leaving its DNS addresses, 103.86.96.100 and 103.86.99.100, on an active interface after the default route disappeared. The DNS failure reportedly reproduced twice, lasted more than 15 minutes without intervention, and resolved in about seven seconds after the interface DNS addresses were reset; this concerns Windows/WSL, not the Linux client.
Temporary workaround while the fix is pending
Users affected by the issue can try turning off DNSSEC for the NordLynx interface with sudo resolvectl dnssec nordlynx off. NordVPN also offers custom DNS addresses in the app as another temporary option. The command changes DNSSEC for that interface. It does not install the permanent fix.
Reinstalling network packages or repeatedly restarting a router is unlikely to help when the reported failure is tied to DNS resolution on the VPN interface. Avoid unverified utilities as workarounds. The connection problem is frustrating, but an unknown privacy tool can bring a separate risk.
A separate NordLynx problem documented by NordSecurity concerns Meshnet transfers, not this DNSSEC failure. Large transfers may stall when MTU is below 1500. The report points to missing MSS clamping and MTU configuration. Its suggested temporary adjustment is sudo ip link set dev nordlynx mtu 1400, but the setting resets when the interface is recreated, as described in the NordLynx MTU issue.
NordVPN says developers are preparing the permanent fix for version 6.0.0. Until it arrives, the DNSSEC command offers a targeted workaround. Users should undo manual changes after updating. NordVPN's Linux 6.0 migration guidance says existing automation commands may need replacement with their new-version equivalents. It does not confirm that the DNSSEC problem is fixed or included in 6.0.0.
