David Buchanan: I'd never considered how DNS resolution works on typical linux systems, and now I wish I hadn't.

I'd never considered how DNS resolution works on typical linux systems, and now I wish I hadn't.

you know it's bad when "systemd-resolved" sounds like a positive innovation

I'm very happy that @tailscale.com figured out Linux DNS for me so I don't have to care.

The Sisyphean Task Of DNS Client Config on Linuxtailscale.com A brief history of DNS on Linux systems and what steps we are taking to ensure it is configured consistently in Tailscale 1.8.

You vs The Guy She Told You Not To Worry About

The graph's changed a teeny bit since that post, as we find more bugs and/or cursed configurations. A notable one I recall was container runtimes that bind-mount /etc/resolv.conf, and thus sometimes contains stuff that makes no sense, and also can't be atomically overwritten with mv(1)

Oh god

saving for reasons

I made this in 2014. It's still completely relevant.

📌

that is one of those horrors you spot in your periphery every once in a while but you dare but look directly at it lest you see too much...

and if *this* is bad, just try and think about how it is on macOS or Windows. betcha can't name what component reads HOSTS.TXT

yeah I just pretend non-linux OSes don't exist

now you possess another cursed knowledge

Including nsswitch.conf or not 😁?

DNS resolution: we know some things, and know who to ask if we don’t know those things.

welcome to hell

Curse of Linux and *BSD is ancient architecture that doesn't work today and has major problems.

I kinda want to know now

You really, REALLY don't

The bane of my existence some days

Post