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.

Sign up for GitHub

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

Jump to bottom

feature: Gracefully handle truncated DNS responses for dnsaddrs #1837

Open
MarcoPolo opened this issue Oct 22, 2022 · 1 comment
Open

feature: Gracefully handle truncated DNS responses for dnsaddrs #1837

MarcoPolo opened this issue Oct 22, 2022 · 1 comment

Comments

@MarcoPolo
Copy link
Collaborator

If the dnsaddr response is over 512 we may see a truncated version of the response. In this case, it would be nice if we could use what we did get rather than completely fail. See: https://github.com/protocol/bifrost-infra/issues/2174 for some context.
@marten-seemann
Copy link
Contributor

What would it take to make this happen? Can you point to the code path where this is triggered?

@dennis-tra dennis-tra mentioned this issue Nov 25, 2022
Closed
@marten-seemann marten-seemann mentioned this issue Dec 14, 2022
Open
3 tasks
@lidel lidel mentioned this issue Sep 23, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MarcoPolo @marten-seemann