BarkBarklington

> Same deal if you ping an IP address (e.g. `ping 8.8.8.8`) or only for domain names? **_so it looks like ping to IP addresses work but ping to domain...

> Same deal if you ping an IP address (e.g. `ping 8.8.8.8`) or only for domain names? ``` base ❯ ping aws.amazon.com (base) ping: aws.amazon.com: Temporary failure in name resolution...

> Could you please send a problem report through the app or check `/var/log/mullvad-vpn/daemon.log` for errors related to DNS? I didn't even realize that I could send a problem report...

> [@BarkBarklington](https://github.com/BarkBarklington) Any updates on this? Sorry I didn't get notifications that you were asking for updates When I get back to my desktop I will upload the logs

> Sounds like a DNS issue. Does running `sudo nano /etc/resolv.conf` and adding "nameserver 10.64.0.1" while Mullvad is connected fix the issue? Once I get back to my desktop I...

> Instead of an additional entry, I was thinking about replacing the original entry. Something similar happens to me in Gentoo, so I thought it may be of help. >...

> Could you please send a problem report through the app or check `/var/log/mullvad-vpn/daemon.log` for errors related to DNS? `System information: id: 297112dc-ab13-4da3-adde-82f9ef0e9258 kernel: 6.17.3-3-cachyos mullvad-product-version: 2025.10 nm: 1.54.1 os:...

> nameserver 10.64.0.1 strangely, this is my current resolve conf file `nameserver 100.64.0.7 options edns0 options trust-ad `

> nameserver 10.64.0.1 strangely, every time i try & edit & save the file, every time i open the file it mysteriously goes back to the original values

❯ sudo systemctl stop systemd-resolved Stopping 'systemd-resolved.service', but its triggering units are still active: systemd-resolved-monitor.socket, systemd-resolved-varlink.socket I then try an edit the file again & it's back to being unchanged...