# DNS in Kubernetes (CoreDNS)

<figure><img src="https://4081356430-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfpkGw9BiJgzxmKhSpJNH%2Fuploads%2FFjcxBzEJY1ix7RXHvYjc%2Fimage.png?alt=media&#x26;token=311889a3-5d4b-44de-876c-6803ad713019" alt=""><figcaption><p>How CoreDNS query works</p></figcaption></figure>

Kubernetes DNS (Domain Name System) provides service discovery and name resolution capabilities within a Kubernetes cluster. It allows applications and services running on the cluster to communicate with each other using their respective names instead of hardcoding IP addresses, which makes the cluster more scalable, maintainable, and dynamic.

Here's a step-by-step explanation of how Kubernetes DNS works:

1. Pod and Service Creation: When you create a Pod or a Service in Kubernetes, each of them gets assigned a unique DNS name.
2. DNS Naming Format:

   * Pods: The DNS name of a Pod takes the form: `<pod-name>.<namespace>.pod.cluster.local`
   * Services: The DNS name of a Service takes the form: `<service-name>.<namespace>.svc.cluster.local`

   Here, `<pod-name>` is the name of the Pod, `<namespace>` is the namespace where the Pod or Service is located, and `cluster.local` is the default DNS suffix for the cluster.
3. DNS Resolution for Pods: When one Pod needs to communicate with another Pod within the same cluster, it can do so using the Pod's DNS name. The DNS resolution process starts with the Pod querying the Kubernetes DNS service (typically running on `kube-dns` or `coredns` pods). The DNS service has access to the cluster's Service and Pod IP addresses.
4. DNS Resolution for Services: When a Pod needs to communicate with a Service, it can use the Service's DNS name. Kubernetes DNS resolves the Service DNS name to the corresponding set of IP addresses of the Service endpoints. These endpoints are typically the IP addresses of the Pods backing the Service.
5. Load Balancing: Kubernetes DNS provides a level of load balancing for Services. When multiple Pods back a Service, the DNS resolution returns multiple IP addresses. The client (calling Pod) can use one of these IP addresses to communicate with the Service. Kubernetes handles load balancing across the selected Pods.
6. Automatic Updates: Kubernetes DNS automatically updates the DNS records whenever Pods or Services are created, deleted, or scaled. This ensures that the DNS system stays in sync with the current state of the cluster.
7. Custom DNS Configurations: Kubernetes allows you to configure custom DNS options for your cluster. For example, you can set up additional DNS nameservers or search domains to resolve external DNS queries or utilize other DNS services.

In summary, Kubernetes DNS simplifies the process of service discovery and communication between Pods and Services within a Kubernetes cluster by providing a dynamic and scalable naming system. This abstraction helps maintain the decoupling between services and enables smooth scaling and management of applications within the cluster.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.farizizwan.com/devops-and-devsecops/kubernetes/fundamental/dns-in-kubernetes-coredns.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.