I don’t think it was ever completely broken for me - just seemed inconsistent, like the caching wasn’t working, some hosts resolved and some didn’t.
As a quick sanity check, can you change /etc/resolv.conf (either change symlink to a different file, or just edit it… it’s a symlink for me right now):
ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 37 Jul 4 23:50 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf
Inside it will look like:
I think there should also be a file: /run/systemd/resolve/resolv.conf that has your “real” DNS IP (form DHCP, etc) in it [note 192.168.13.1 is just my router’s IP, probably different for you]:
So, this will link to the one that doesn’t use systemd.resolv proxy:
sudo rm /etc/resolv.conf && sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
(alternatively edit the existing one and add something like “nameserver 22.214.171.124” before the other nameserver line, just for testing…)
If everything now works, it’s definitely systemd.resolv related.