Setting up NextDNS on Ubuntu in resolved.conf doesn't work with VPNs DNS
I followed the recommended setup guide for Linux, which is overriding the /etc/systemd/resolved.conf file with what's provided in NextDNS web UI; however, when this is setup, private ips that are only known on VPNs are no longer resolved, written in a simpler way, setting up NextDNS does not allow VPNs to use their own DNS servers and resolve properly.
This might not be a bug with NextDNS itself (feel free to move it if that's not the case) but I feel that being given that configuration as Recommended, and breaking other things is not what I would call expected behavior.
Let me know if anybody else has faced a similar behavior and know a fix.
NextDNS has been a beat down. I started this a week ago and NOTHING matches what they have documented. The CLI instructions are cryptic and if you ask a question you get a condecending answer thatas more crypted from a dev. Its not worth it. I can kiss that money goodbye
Mine resolved.conf looks like this:
Not using ipv6 here, if you do you should enable them to.
restart the service after changing the file.
Some (DOH) DNS services are blocked on VPN services.
Thanks for the responses so far.
What I've found after further investigation is that the issue lies mainly within the network-manager-openvpn plugin, which doesn't implement a lot of openvpn client features.
Another reason for VPN DNS not working is setting the following configuration:
Because the VPN DNS does not rely on DoT protocol, the system won't use it at all due to that config.
Instead I'm setting the config as:
This allow's non DoT servers to work as well, the only drawback being NextDNS page does not recognize the device as "This device is using NextDNS with this profile.", even if the logs are showing up.
Will keep testing but the configuration as opportunistic works better for me.
- 2 mths agoLast active