Conversation
toke

Toke Høiland-Jørgensen

Got a notification from my registrar that I was using an outdated DNSSEC key algorithm for my domain, so decided to re-learn how DNSSEC signing actually works in Bind.

Discovered that there's now a mode where Bind will manage keys and signing automatically. Yay! Only problem is, the domain in question was not configured that way.

Decided to use the occasion to swap over the config to that mode. Which of course caused Bind to generate new (managed) keys without doing any of the smooth gradual rollover that it otherwise implements. Oops!

Ah well, everything is set up correctly now, and it'll only be a single TTL until the whole world agrees. Should be fine; right? 😅

#DNS #DNSSEC #OpsFail
1
0
3
dwm@mastodon.social

Dr. David McBride (dwm)

Reply to @toke

@toke Ah, I am too late to point you to this very helpful write-up of how to migrate gently from one mode to another written up by the esteemed @fanf — hopefully useful to anyone else following in your footsteps!

https://dotat.at/@/2024-05-11-dnssec-policy.html

1
0
0
toke

Toke Høiland-Jørgensen

Reply to @dwm@mastodon.social
@dwm @fanf yes, this does indeed look like that I should have done. Ah well 🤷‍♂️
1
0
1
dwm@mastodon.social

Dr. David McBride (dwm)

Reply to @toke

@toke In role-playing games as in life, "Experience is what you get right after you needed it."

1
0
0
toke

Toke Høiland-Jørgensen

Reply to @dwm@mastodon.social
@dwm haha, yes indeed. Now, to figure out how to remember this when I next have to pay attention to it in another decade or so...
1
0
0
drscriptt@oldbytes.space

DrScriptt

Reply to @toke

@toke @dwm personal / private journal entry or public blog article?

1
0
0
toke

Toke Høiland-Jørgensen

Reply to @drscriptt@oldbytes.space
@drscriptt @dwm that's not a bad idea, actually!
0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: