-
Notifications
You must be signed in to change notification settings - Fork 137
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
Properly proxy truncated responses #467
Conversation
Can one of the admins verify this patch? |
Truncation state is being reset here:
|
9feac1e
to
21f08ec
Compare
I've confirmed, using tcpdump / wireshark, that the last patch causes |
Looks like the failure may be unrelated to my change |
@timcharper rebasing should help - some changes to circle.yml and other fixes have been committed since you forked |
Before updating the DNS client, no answers were sent when a truncated response was received from downstream. After updating the DNS client, it would work properly, but it log the error and then (needlessly) continue to attempt the other DNS servers listed. This change causes mesos-DNS to ignore the truncated response error from the mesos-DNS client, and send whatever response it received. TODO - the truncated bit state should be forwarded, and not cleared. Fixes mesosphere#457
@drewkerrigan thanks; I have rebased |
Thank you for splitting commits! |
Do you have an idea on how to simply get truncated replies out of dnsmasq? |
@sargun the way I replicate the issue is using weave DNS. I run 14 containers or so with the same weave host name and it serves them truncated |
(Weave DNS does not compress responses so it is easier to replicate) |
@timcharper I'll recreate this issue over the coming week. Would anyone be interested if we had an integration test that propped up a dns server? |
🎉 |
Fixes #457