systemd strikes again with systemd-resolved...

systemd must be the worst thing ever invented. It started off being a good replacement for old rc startup scripts, but has since evolved into a monstrocity that makes Linux unusable. The latest nonsense is call systemd-resolved. It's apparently there to deal with a local resolver for things that can not support NSS, like Chrome.

Not only does this seems rather silly, for something I clearly do not care about at all, but it's also detrimental when your app does its own resolution. In my case, Apache Traffic Server fails to run its regression when it finds this local resolver ...

The solution was simple for me, just disable this useless systemd service:

$ sudo systemctl disable systemd-resolved.service

 

Hacking: