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

proto: Increase the maximum request depth to 26 #1736

Merged
merged 1 commit into from
Jul 12, 2022

Conversation

wiktor-k
Copy link
Contributor

OPENPGPKEY requests in the wild has been found to exceed the maximum request depth (20) partially due to parallel requests that increase the counter by 2 or 4.

Increasing the value to 26 allows these requests to succeed. The test vector used to validate this change is a validating request for OPENPGPKEY records for the following name:

A47CB586A51ACB93ACB9EF806F35F29131548E59E2FACD58CF6232E3._openpgpkey.debian.org

See: #1735

OPENPGPKEY requests in the wild has been found to exceed the maximum
request depth (20) partially due to parallel requests that increase the
counter by 2 or 4.

Increasing the value to 26 allows these requests to succeed. The test
vector used to validate this change is a validating request for
OPENPGPKEY records for the following name:

    A47CB586A51ACB93ACB9EF806F35F29131548E59E2FACD58CF6232E3._openpgpkey.debian.org

See: hickory-dns#1735
Copy link
Member

@bluejekyll bluejekyll left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this. We can merge as is. It would be nice for us to go back and figure out why the RequestOptions isn't being passed through properly.

@bluejekyll bluejekyll merged commit 7dcb7b9 into hickory-dns:main Jul 12, 2022
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

Successfully merging this pull request may close these issues.

None yet

2 participants