You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting/disconnecting to the mullvad VPN (official package, 2023.3), the DNS stops working, and I need to restart the service to have it working again.
> dig example.com
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: timed out
; <<>> DiG 9.18.19 <<>> example.com
;; global options: +cmd
;; no servers could be reached
I have mullvad start after nextdns (as a part of a desktop autostart).
Logs and trace are below:
(Tailscale errors on both are because tailscale starts on boot before nextdns, and nextdns doesn't get internet connectivity for a bit more I guess)
These are on machine boot, as I took these before I narrowed it down to the auto-connecting VPN
Hmmm... my system config has any external DNS being disabled, and mullvad would block any outgoing port 53, so it is possible that the app cannot reach a DNS server to bootstrap itself.
Context
<Describe the bug>
I am using the nextdns service in nixos with the latest package from unstable.
The service looks like this:
cat /etc/systemd/system/nextdns.service
When connecting/disconnecting to the mullvad VPN (official package, 2023.3), the DNS stops working, and I need to restart the service to have it working again.
I have mullvad start after nextdns (as a part of a desktop autostart).
Logs and trace are below:
(Tailscale errors on both are because tailscale starts on boot before nextdns, and nextdns doesn't get internet connectivity for a bit more I guess)
These are on machine boot, as I took these before I narrowed it down to the auto-connecting VPN
nextdns log
https://pastebin.com/eg25z1mn
nextdns trace
https://pastebin.com/q3FmYvTD
These are when booting with VPN off, then turing it on (also stalls)
nextdns log
https://pastebin.com/9qrmhaa0
nextdns trace
https://pastebin.com/Gz1nz64h
config:
The text was updated successfully, but these errors were encountered: