-
Notifications
You must be signed in to change notification settings - Fork 460
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 resolution for externalName services broken in v1.14.9 #224
Comments
I can confirm DNS resolution for externalName service is broken in 1.14.9 but working in 1.14.8. Though with 1.14.9, I can also see the externalName record is generated in kubedns logs:
Will spend more time. |
Got some pointers, seems like the nameserver for skydns somehow gets reset to empty, instead of using the ones listed in /etc/resolv.conf.
|
Also found out why our e2e test didn't catch this. Turned out in the externalName test we deliberately dig for just CNAME record. So the CNAME -> A (or AAAA) record path in upstream server is not examined. |
@grayluck is working on a fix. |
For the record, query for PTR records that only exist in upstream server seems to be broken as well. |
kube-dns 1.14.10 is released with the fix. |
Confirming that it works with v1.14.10. |
After updating to v1.14.9, externalName services are not resolving anymore. I tested with v1.14.8 and it works.
kube-dns pod logs (I've replaced the correct domain with example.com but it exists and resolves normally in v1.14.8):
I initially thought it's regression from #210 but I'm not sure. Please let me know how I can help with any more debug info.
The text was updated successfully, but these errors were encountered: