-
Notifications
You must be signed in to change notification settings - Fork 361
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Linux] DNS resolution via systemd-resolved broken #7452
Comments
Beware of: Thus, I see your issue more of a problem with your device and not a problem caused by Mullvad VPN. fyi, I am a fellow Mullvad customer. I don't speak for Mullvad. |
Perhaps, Mullvad could publish an article on what to consider for systemd systems. |
And, beware that Archlinux isn't an officially supported Linux distro. Only Ubuntu, Debian and Fedora are. |
Hmm. Seems like this can happen if mullvad-daemon was previously managing dns directly through
We should probably implement this in the daemon though. edit: updated commands with duxscos suggestion |
Also the log message should be improved. |
@hulthe Beware that Those three seem to be the only ones to consider:
Source: https://www.freedesktop.org/software/systemd/man/latest/systemd-resolved.html |
Is it a bug?
I have checked if others have reported this already
Current Behavior
The DNS resolution via systemd-resolved is broken as can be seen in the log output.
I also checked the /etc/systemd/resolved.conf file and can confirm that mullvad is NOT writing the DNS server to that file.
In order to get the DNS resolution to work, I need to manually set the IP for the desired dns server in that file.
Expected Behavior
The DNS resolution via systemd-resolved should work.
In case of an error, such as this, there sould be more detailed output to be able to locate the cause of the issue. At the moment, it only says "systemd-resolved operation failed".
What is the exact command that mullvad is trying to execute, that leads to this error?
Steps to Reproduce
Unsure because the log message does not provide enough information...
Please kindly advise me how to find out what exactly mullvad is trying to execute, so that I can debug this further.
I know for a fact, that systemd-resolved itself is working as I am currently using it for the DNS resolution. I did however have to set the desired DNS server manually in the /etc/systemd/resolved.conf file, otherwise it would not be working because - for an unknown reason - mullvad is failing to do so.
Failure Logs
[talpid_core::dns][INFO] Setting DNS servers: Tunnel DNS: {} Non-tunnel DNS: {[REDACTED]} [talpid_core::dns::imp][DEBUG] Can't manage DNS using systemd-resolved: systemd-resolved operation failed
Operating system version
Archlinux
Mullvad VPN app version
2025.2
Additional Information
No response
The text was updated successfully, but these errors were encountered: