In the previous chapters, we've configured services and connected applications across our cluster, relying on stable endpoints to reach our deployments. However, IP addresses change when pods restart and services get recreated. This is where DNS becomes crucial; it provides a reliable way for applications to discover and communicate with each other by name rather than memorizing constantly changing IP addresses. This chapter explores Kubernetes' internal DNS system, CoreDNS, which automatically maintains name resolution for all services and pods in our cluster.