Lightning Talk
summary
Creating an ExternalName service named default that points at a dummy domain via kubectl causes short names like hello-world.http.default to resolve to that dummy target and fail, while the fully qualified domain name still works. Diagnosis uses dig from an Ubuntu sleep pod to inspect answers and reveals Kubernetes’ DNS search path plus ndots=5 causes unintended suffixing and a CNAME to the dummy domain. Fixes: use FQDNs or set ndots=1 / restrict pod DNS options.
AI-written summary · about
related talks
06mLightning Talk: Is Your Kubernetes Cluster's DNS Working?
27mCoreDNS Deep Dive
34mIt’s Always DNS: So Let’s Break It On Purpose
03mLightning Talk - Introducing CoreDNS Kubernetes Integration
38mIntro + Deep Dive: CoreDNS
35mOMG Namespaces!
32mDemystifying DNS: A Guide to Understanding and Debugging Request Flows in Kubernetes Clusters
34mRethinking the K8s DNS for the Modern Enterprise