[04:52] <jdb10> Hi all. Xubuntu 23.04 name resolution woes! Well, really the last few versions. I had issues a version or where if I started a VPN (protonvpn app) and failed to stop it before rebooting, name resolution quits working. A version or two ago I could manually edit /etc/resolv.conf to replace 127.0.0.3 with 8.8.8.8, which would work until reboot, but
[04:52] <jdb10> now that doesn't even work. I can ping 8.8.8.8, but can't ping to urls. I know /etc/resolv.conf points to a stub file deep in systems land that does magic that's supposed to do magic, but I have no idea how to fix it if it's broken. Can anybody point me in the right direction?
[04:56] <Unit193> ls -lh /etc/resolv.conf  and see where it points?
[04:57] <Unit193> Are you using systemd-resolved?  Does the application have support for resolvconf?  Does openresolv work any better with it?
[05:03] <jdb10> It points to /run/systems/resolve/stub-resolv.conf, which probably means I am. I haven't tried resolving or openresolv because I don't know how to replace systemd.resolved. This happened a few weeks ago as well, I tried doing the deep dive with zero success and wound up just reinstalling xubuntu latest version. Not disastrous because of how I have
[05:03] <jdb10> the partitions set up, but still a bit of a pain.
[05:06] <Unit193> Yeah sorry, I can't help.  Years back when systemd-resolved was default, I never had DNS working.  Removing it always fixed the problem for me and with the disadvantages of it I'm not interested in it now.  But it clearly works for some people, soooo I guess good for them? :)
[05:06] <Unit193> resolvconf and openresolv are just interfaces to /etc/resolv.conf, I've had the best luck with the latter, works well with wireguard-tools too.
[05:07] <Unit193> I think you can use resolvctl to see what the actual DNS you're using is?
[05:08] <Unit193> resolvectl → Current DNS Server: and DNS Servers:
[05:10] <jdb10> I just found something that worked, god help me. I used the ip address of my router, so I'm back to updating resolv.conf all the time. Think I'll screw around with this on a throw-away virtual machine and see if I can come up with a long-term solution!
[05:10] <jdb10> Thanks, though...