-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kubernetes not working with DNS - no communication from pod to outside world #983
Comments
Found the problem which exists in DNS (ip adresses works ok. Helped me config map for dns:
|
I am stuck at the same exact place , I tried giving google dns and corp dns it still fails. Any suggestions ? |
This same issue happens to us with minikube 0.23.0, Kubernetes 1.7.5, and Ubuntu 18 (bionic). DNS names don't resolve. The workaround for putting We still have to figure out a way to tweak our minikube setups to apply this workaround until this gets fixed. |
From inside busybox pod after applying upstreamServer config @lukaszpy mentioned above I get the following for external nslookups (minikube v0.28.1 on ubuntu 18.04): / # nslookup 8.8.8.8 Non-authoritative answer: / # nslookup google.com Non-authoritative answer: *** Can't find google.com: No answer / # When I attempt kubernetes.default, I get this: ** server can't find kubernetes.default: NXDOMAIN *** Can't find kubernetes.default: No answer / # |
I experience the same problem, though my YAMLs look different than the provided snippet. Can I still apply the workaround somehow? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
no longer an issue |
I have probaly problem with kubernetes DNS as my service cannot communicate to outside world (bitbucker.org).
Actually I found this page:
https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/
and validate it on my cluster (no minikube):
and:
Any idea how can I resolve to be able connect from inside pod to outside world ?
This probably is related to Flannel, as connectivity from image run only by docker is avalible.
Whant to mention that I have run my cluster with this example: https://blog.alexellis.io/kubernetes-in-10-minutes/
I have also modify https://github.com/coreos/flannel/blob/master/Documentation/kube-flannel.yml
and pass argument --iface with my wifi card which has acces to internet but then kube-flannel-ds cannot start
from:
to:
Master node:
Node worker:
Envirnoment:
The text was updated successfully, but these errors were encountered: