DNS, Private DNS, and Service Discovery: How Servers Find Each Other

In distributed systems, servers cannot intuitively locate one another, making address resolution a foundational infrastructure challenge. DNS (Domain Name System) solves this by translating human-readable names like google.com into machine-usable IP addresses, enabling browser-to-server communication in milliseconds. For internal services such as databases and message queues that should never be publicly exposed, Private DNS provides an internal-only directory accessible solely within a private network or VPC. Rather than hardcoding IP addresses — which change as containers move or instances restart — engineers assign stable internal hostnames like postgres.internal, letting DNS handle routing transparently. This principle underpins broader service discovery tools including Consul, Eureka, Kubernetes DNS, and service meshes used across modern cloud architectures.