F33 DNS from VPN is not longer in use after upgrad

Hello, I’ve seen multiple topics regarding VPN issues but cannot find solution there.
I’ve created ovpn connection via NM gui.
Server could be resolved over both public DNS(expected 403) and DNS from VPN(the only way to get access to resource).
Use this connection only for resources on its network is turned on.
Previously DNS from VPN was prioritized over system DNS with this checkbox turned on, but now it tries to resolve over system one first (which have no sense for my with my limited networking knowledge).

1 Like

Route all DNS:
Systemd-resolved not querying DNS server set by openvpn

Or use split DNS:
DNS problems after upgrade Fedora 33

2 Likes

How can I find VPN_ID?

See connection name:

nmcli connection show
1 Like

Thanks!
Could you please describe in 2 words what this command do?

1 Like

It makes use DNS over VPN for all domains replacing resolvers from other connections.

1 Like

Am I missing something? no such user or named directory: .

If I understand correctly this command modify connection lowering dns priorities. If it’s true I should lover dns priorities for wired connection in order to use VPN first.

Apparently you need to use quotes or backslash to escape tilda when working in zsh.
Or run that command with bash.
Negative values have higher priority.

1 Like

Indeed. Is there a declarative way to check DNS priorities?

1 Like
resolvectl dns
resolvectl domain 
1 Like

The ~. syntax is only known by resolvectl, you cannot use it in NetworkManager AFAIK.

No, it works, see: Systemd-resolved not querying DNS server set by openvpn