mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #319] Incorrect truncation #145
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#145
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vorner on GitHub (Dec 17, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/319
This seems to be wrong: https://docs.rs/trust-dns/0.13.0/trust_dns/op/struct.Message.html#method.truncate. I haven't read the RFCs in a while, so I don't remember which one it was, but as I remember, the idea with truncation was to put as much as fits into the message (depending on the size of the buffer).
AFAIK it is usually done during writing of the message to the output buffer ‒ it is being written from the beginning and if something doesn't fit, it returns back and flips the bit.
@bluejekyll commented on GitHub (Dec 17, 2017):
Yes, we could definitely be a little less aggressive on the truncation. I think the size of the output buffer should respect EDNS. After that, we can then implement what you suggest. It will require some trimming of the outbound buffer. I have some new methods coming on BinEncoder that should make this easier.