From the course: Debugging Kubernetes

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Conquering DNS misconfigurations within Pods

Conquering DNS misconfigurations within Pods - Kubernetes Tutorial

From the course: Debugging Kubernetes

Start my 1-month free trial Buy for my team

Conquering DNS misconfigurations within Pods

“

- [Instructor] Ah, DNS, the cause and solution of all networking problems. Now imagine this, you've just deployed your app into a Kubernetes-powered integration environment for final testing before a release. Since all of your tests passed locally, you're expecting these tests to easily pass. A few minutes later you get an email telling you that your tests have failed. How could this happen? Upon looking at logs generated during your CI/CD pipeline, you see lots of errors that look like this NXDOMAIN error that you see here. But how is this possible? DNS was working just fine locally and in our dev environment. Well, there are a million reasons why you might find yourself in this situation outside of Kubernetes. But within Kubernetes, there are usually three common causes. Either the pod has a custom but broken DNS configuration, the pod is running an older version of Alpine Linux that doesn't play nicely with DNS within Kubernetes, or DNS within the cluster is just plain broken. Just…

Contents