Skip to content
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

Parallel queries aren't handled correctly #4

Open
kunpw opened this issue Oct 10, 2020 · 2 comments
Open

Parallel queries aren't handled correctly #4

kunpw opened this issue Oct 10, 2020 · 2 comments

Comments

@kunpw
Copy link

kunpw commented Oct 10, 2020

When jDnsProxy receives two or more parallel queries over UDP, for example, parallel queries of A and AAAA records of one domain over UDP, the default behavior on many Linux installs, the response for the last query in this series will be used as responses to all queries in this series.

This leads to wrong caching as well.

@moparisthebest
Copy link
Owner

What is incorrect about the response?

@kunpw
Copy link
Author

kunpw commented Nov 21, 2020

Let me give an examaple. It's been some time so my memory could be inaccurate.

Time MessageID SrcPort DestPort Query/Response
1 32124 10000 53 A firefox.settings.services.mozilla.com
1 32125 10000 53 AAAA firefox.settings.services.mozilla.com
1 32126 10001 53 A github.com
1 32127 10001 53 AAAA github.com
1 32128 10002 53 A example.com
1 32129 10002 53 AAAA example.com

2 32129 53 10000 AAAA example.com 10.222.222.222
2 32129 53 10000 AAAA example.com 10.222.222.222
2 32129 53 10001 AAAA example.com 10.222.222.222
2 32129 53 10001 AAAA example.com 10.222.222.222
2 32129 53 10002 AAAA example.com 10.222.222.222
2 32129 53 10002 AAAA example.com 10.222.222.222

As you can see, the response for the last query in this series is used as responses to all queries in this series.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants