-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
dump_cache truncates large records #981
Comments
dyunwei
pushed a commit
to dyunwei/unbound
that referenced
this issue
Jan 9, 2024
dyunwei
pushed a commit
to dyunwei/unbound
that referenced
this issue
Jan 9, 2024
wcawijngaards
added a commit
that referenced
this issue
Jan 9, 2024
Fix #981: dump_cache truncates large records.
wcawijngaards
added a commit
that referenced
this issue
Jan 9, 2024
jedisct1
added a commit
to jedisct1/unbound
that referenced
this issue
Jan 14, 2024
* nlnet/master: Changelog note for NLnetLabs#988. - Merge NLnetLabs#988: Fix NLnetLabs#981: dump_cache truncates large records. Fix NLnetLabs#981: dump_cache truncates large records.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When dumping the unbound cache, some large records are truncated and there is no newline between those and the next rrset entry, resulting in a corrupt dump file, that cannot be loaded back to unbound.
To reproduce
Steps to reproduce the behavior:
_p.3.1o586rh._u.taylorandfrancis.com._spf.smart.ondmarc.com
. The answer currently is something like:_p.3.1o586rh._u.taylorandfrancis.com._spf.smart.ondmarc.com.
. The entry will be truncated with the next;rrset
appended to it, like:System:
unbound -V
output:The text was updated successfully, but these errors were encountered: