Hacker News new | past | comments | ask | show | jobs | submit login

It likes to fall over to the secondary server, doesn't it.



There are so many known systemd-resolved bugs [1][2] that I can't tell which one was breaking both of my simple Ubuntu desktop machines. Systemd-resolved sets itself up as the sole DNS resolver and then randomly reports it can't reach any DNS servers.

[1] https://github.com/systemd/systemd/issues?q=is%3Aissue+is%3A...

[2] https://www.reddit.com/r/linux/comments/18kh1r5/im_shocked_t...


Yes and... the tools are now highly distro-specific. I don't want to allocate my study time to resolvectl, I want to allocate it to programming, but my home server requires me to be a beginner again in something that was easy a decade ago. And I am not getting anything of value for that trade.


It likes to botch things.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: