Starting with GKE version 1.36, the default engine for kube-dns is CoreDNS
Share
Services
## Issue
Issue
Starting with GKE version 1.36, the default engine for kube-dns is [CoreDNS](https://coredns.io/). For Pod IP DNS queries in the `<a-b-c-d>.<namespace>.pod.cluster.local` format, CoreDNS returns NXDOMAIN if the specified `<namespace>` does not exist. The legacy `kubernetes/dns` implementation skipped checking the existence of the namespace provided in the `<namespace>` segment in these queries.
Queries in the `<a-b-c-d>.<namespace>.pod.cluster.local` format are not part of the[Kubernetes DNS specification](https://github.com/kubernetes/dns/blob/master/docs/specification.md). We can't guarantee that uses outside of those specified in the DNS spec will remain consistent across releases.
Mitigation:
* **Recommended**: Migrate to supported headless Service DNS records (`<hostname>.<subdomain>.<namespace>.svc.cluster.local`).
* **Workaround**: Ensure the `<namespace>` specified in the DNS query exists in the cluster.
What else is happening at Google Cloud Platform?
Read update
Services
Share
Read update
Services
Share
Bulk registration of discovered services and workloads to an App Hub
about 5 hours ago
Services
Share
Artifact guard with CI/CD integration is deprecated. It will be shut
about 7 hours ago
Services
Share
Read update
Services
Share