Skip to content
This repository has been archived by the owner on Aug 7, 2020. It is now read-only.

TXT Record Response Ordering #2

Open
dtmsecurity opened this issue Nov 12, 2018 · 0 comments
Open

TXT Record Response Ordering #2

dtmsecurity opened this issue Nov 12, 2018 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@dtmsecurity
Copy link
Contributor

dtmsecurity commented Nov 12, 2018 •
edited
Loading

Some DoH providers appear to reorder TXT responses which is not currently handled when multiple chunks are sent out of sequence in a single DNS response.

For some providers we can keep max_records to 5 which works well but for others we currently have to stick to the default of 1.

A trivial fix would be to mark response order with the first byte. However, there's probably a lot more DNS server optimizations than just this too.
@dtmsecurity dtmsecurity added enhancement New feature or request help wanted Extra attention is needed labels Nov 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dtmsecurity