-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Default $TTL not working correctly on nsd >= 4.10.0 #375
Comments
Thanks for reporting @dfxbb! I'll have a look. |
k0ekk0ek
added a commit
to k0ekk0ek/simdzone
that referenced
this issue
Aug 16, 2024
Use value specified in $TTL directive if available, otherwise use the last stated explicit TTL. Signal whether the TTL is implicit or not via a newly introduced flags parameter to allow for correcting TTL values (or bailing) after deserialization of all RRs. Fixes NLnetLabs/nsd#375.
k0ekk0ek
added a commit
to k0ekk0ek/simdzone
that referenced
this issue
Aug 19, 2024
Use value specified in $TTL directive if available, use the last stated explicit TTL otherwise. Fixes NLnetLabs/nsd#375.
k0ekk0ek
added a commit
to k0ekk0ek/simdzone
that referenced
this issue
Aug 19, 2024
Use value specified in $TTL directive if available, use the last stated explicit TTL otherwise. Fixes NLnetLabs/nsd#375.
@dfxbb, NLnetLabs/simdzone#228 fixes this issue, so it's fixed in the next release. Thanks for reporting! |
@k0ekk0ek Thanks for the timely fix! 👍 |
k0ekk0ek
added a commit
to k0ekk0ek/simdzone
that referenced
this issue
Aug 23, 2024
Use value specified in $TTL directive if available, use the last stated explicit TTL otherwise. Fixes NLnetLabs/nsd#375.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While parsing the zonefile, default $TTL is not used on all RRs with TTL omitted. Instead, it seems that the TTL of the previous record is used.
For example, with this zonefile:
On nsd <= 4.9.1, TTL of the last two A records (ns and www) is 300, as I am expecting.
output of
nsd-checkzone -p example.com /root/example.zone
:But on nsd >= 4.10.0 (test on 4.10.0 and 4.10.1), it became 86400.
The text was updated successfully, but these errors were encountered: