0 views collected around this technical thread.
This article outlines a step‑by‑step solution for exposing pod domain names inside a corporate network using CoreDNS with an etcd backend, including server and agent deployment, configuration, verification, and practical usage recommendations.
This article explains common Kubernetes DNS resolution failures, both for external domains and internal service discovery addresses, and provides a step‑by‑step troubleshooting workflow that includes checking CoreDNS, examining resolv.conf, adjusting DNS settings, and recreating CoreDNS when necessary.
This guide explains common Kubernetes DNS problems—including failure to resolve external domains, inter‑pod service discovery addresses, and related impacts on applications like Nginx reverse proxies—and provides step‑by‑step troubleshooting procedures such as checking CoreDNS, inspecting resolv.conf, and customizing dnsPolicy and dnsConfig in pod specifications.
This article explains the fundamentals of DNS, its role as an application‑layer protocol, and how Kubernetes generates and manages each pod's /etc/resolv.conf through kubelet, covering nameserver, search, ndots options, dnsPolicy choices, and custom dnsConfig examples.
This article explains why CoreDNS may experience DNS resolution timeouts in a Kubernetes cluster, how to analyze logs and timeout settings, locate upstream DNS problems, and apply practical solutions such as adjusting timeout values, switching upstream DNS servers, and deploying a local DNS service.
This article details the motivation, design, implementation, testing, and rollout of a refactored Kubernetes DNS solution that replaces the default kube-dns → CoreDNS chain with a node‑local q‑dnsmasq cache and parallel upstream queries to achieve higher availability, faster resolution, and better cache hit rates in large‑scale clusters.
A sudden Kubernetes outage was traced to a CoreDNS ReadinessProbe failure on port 8181, and the article walks through symptom detection, code‑level root‑cause analysis, and a ConfigMap fix that restores inter‑pod communication.
This article explains Kubernetes service discovery by first covering essential network concepts, then detailing how Services, DNS, Endpoints, and kube-proxy work together to provide stable, load‑balanced communication between dynamic Pods in a cluster.
This article explains how Kubernetes enables service‑to‑service communication using three native objects—ClusterIP Service, CoreDNS for DNS‑based discovery, and Kube‑proxy for DNAT—while abstracting the underlying network complexities from applications.
The article details two high‑availability DNS implementations for Tencent Cloud—an intelligent BIND‑based server and a CoreDNS solution backed by an ETCD cluster—covering DNS fundamentals, installation steps, configuration files, zone creation, health checks, and verification of internal and external name resolution across multi‑AZ deployments.
CoreDNS is a modern, plugin‑based DNS server designed for containerized and Kubernetes environments, offering simple configuration, memory‑safe Go implementation, and tight integration with cloud‑native ecosystems, while also discussing its advantages, limitations, and relationship with the CNCF.
This article explores how Kubernetes resolves DNS queries by examining the Pod's resolv.conf configuration, the CoreDNS service implementation via iptables rules, and the impact of search and ndots options on query behavior, providing practical examples and optimization tips.
This article details Ant Financial's progressive Service Mesh migration plan, explaining the challenges of moving massive legacy applications to Kubernetes and Istio, the evaluated evolution routes, key migration practices like network continuity and DNS-based addressing, and the implementation of custom CoreDNS plugins for dynamic DNS updates.
This article presents a DNS‑based universal addressing solution that enables traditional SOA applications using interfaces such as Dubbo, HSF, and SOFA to run on a Service Mesh without code changes, by mapping interface names to Kubernetes ClusterIP through CoreDNS and leveraging Istio’s routing mechanisms.