coredns doesnt resolve names in kind v0.19.0 #6528
-
Hey folks, trying to run some services in kubernetes-kind and got timeout problems. I assume it's a DNS issue, since ingress controller cant find an upstream:
But this service exists in kubernetes. I've tested the similar on kubernetes service and was surprised:
In configmap I see the default config:
I assume something like
must be resolved, isn't it? |
Beta Was this translation helpful? Give feedback.
Answered by
chrisohaver
Mar 7, 2024
Replies: 1 comment 2 replies
-
dig doesn’t use search domains by default. If you add the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Try enabling logging in coredns to see if the nginx dns requests are reaching coredns.
https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#are-dns-queries-being-received-processed