Hacker News Reader

Oh man, this nightmare situation drove me completely nuts when I was trying to get DNS + VMs working with K8s test scripts.

I ended up writing this series to exorcise the demons:

https://zwischenzugs.com/2018/06/08/anatomy-of-a-linux-dns-l...

https://zwischenzugs.com/2018/06/18/anatomy-of-a-linux-dns-l...

https://zwischenzugs.com/2018/07/06/anatomy-of-a-linux-dns-l...

https://zwischenzugs.com/2018/08/06/anatomy-of-a-linux-dns-l...

View on HN

I'm more and more leaning towards "run dnsmasq on every single machine and be done with it", it feels like the sweet sweet spot to get flexibility and the predictability. Otherwise, systemd-resolved is not as unpredictable and frustrating as resolvconf or networkmanager.

> "run dnsmasq on every single machine and be done with it"

Haha this is what I do…

> Otherwise, systemd-resolved is not as unpredictable and frustrating as resolvconf or networkmanager.

NetworkManager uses dnsmasq or systemd-resolved as it's backend...

Isn’t systemd-resolvd using dnsmasq under the hood?

No, systemd-resolved does its own thing independently.

I loved that series, thank you! The DNS system on Unix-like systems is such a complicated mess.

Personally, I've set adsuck and my /etc/resolv.conf points to 127.0.0.1

Reply on news.ycombinator.com