In a Headless service, how does DNS resolution typically represent the endpoints?

In a Headless service, how does DNS resolution typically represent the endpoints?

• A. DNS returns a single IP that load-balances across pods.
• B. DNS resolves to an external address for the service.
• C. DNS returns a list of Pod IP addresses (one per endpoint).
• D. DNS is not used for Headless services.

Answer: (C)

Headless services omit the cluster IP, so there’s no single virtual IP to balance to. Instead, the DNS name for the service returns the actual endpoints behind it. Practically, you get multiple A (and possibly AAAA) records, each one pointing to a Pod IP—one per endpoint. This lets clients either connect directly to a specific pod or implement their own load-balancing strategy. As pods scale up or down, the DNS answers update to reflect the current set of pod IPs.

Headless services omit the cluster IP, so there’s no single virtual IP to balance to. Instead, the DNS name for the service returns the actual endpoints behind it. Practically, you get multiple A (and possibly AAAA) records, each one pointing to a Pod IP—one per endpoint. This lets clients either connect directly to a specific pod or implement their own load-balancing strategy. As pods scale up or down, the DNS answers update to reflect the current set of pod IPs.