-
Notifications
You must be signed in to change notification settings - Fork 760
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
DNS doesn't seem to able to look up external addresses #1975
Comments
If I disable ha-cluster, this works as expected:
|
Whilst writing the attached test, it to be working okay, without disabling HA on my local machine so might be a cloud issue. |
This is due to a @ktsakalozos can you please attach the PR where this was fixed? |
Fixed in #1985 |
I have this exatcly problem with version v1.23.3 on debian 11 in a ha setup with 3 nodes. Dns pod and service are running correctly. Any help about this? |
I got this error with Microk8s v1.24.3 on CentOS 7.9.2009 kubectl exec -i -t dnsutils -- nslookup kubernetes.default
;; connection timed out; no servers could be reached
command terminated with exit code 1 UpdateI managed to solve the issue by enabling ip masquarade firewall-cmd --add-masquerade --permanent
firewall-cmd --reload as I mentioned it in #2407 (comment) |
DNS debug found here https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/
But can't seem to get anything outside:
The text was updated successfully, but these errors were encountered: