cross-posted from: https://lemmy.ca/post/45140185

I was able to literally 1 hour ago.

I changed my DNS from Next DNS to CIRA Canadian Shield (Protected) to test it out.

Then I was only able to connect to the internet through Mulvad VPN.

Then I changed back to Next DNS and I observe the same behaviour.

How do I determine what is causing the problem?

How do I solve it?

  • HelloRoot@lemy.lolEnglish
    7·
    8 days ago

    My stupid guess would be that you have a kill switch from your VPN and it might not have anything to do with your DNS. But also, have you rebooted?

    Do you use dnscrypt-proxy or systemd-resolved or something else?

    Also check your /etc/systemd/resolved.conf

  • phanto@lemmy.caEnglish
    3·
    8 days ago

    I use ProtonVPN and it sets up a “leak shield” interface when you start it and destroys that when you end it. It keeps traffic from flowing out over the non-vpn internet. The problem is, if the VPN crashes or doesn’t shut down gracefully, that interface kills all traffic.

    To test if it’s something like that, try pinging an outside address, first by name and then by IP. If you can’t get either, it’s not the DNS messing you up. If you CAN ping the IP but not the name, then it is the DNS messing you up.

  • Steamymoomilk@sh.itjust.worksEnglish
    2·
    8 days ago

    In your wiregaurd config (assuming your not using an app) you may have iptables that makes a killswitch when the interface is up.