Why DNS belongs in user hands, not infrastructure code

A developer argues DNS should be a human-readable interface layer for people, not a tool for automated systems to discover services. The idea challenges how many modern architectures (service meshes, Kubernetes) treat DNS as machine infrastructure—suggesting a cleaner separation might reduce complexity and failure modes for indie builders managing their own stacks.