I’ll let you guess what daemon is deprecated, and what daemon is the new one you’re supposed to use in OpenBSD.
Oh, that's sad. I take it you've tried signalling rad to reload its configuration when a prefix on interfaces it advertises changes? IIRC, that's how you instruct radvd to do the thing.
Anyway, if that doesn't do what you need, then I don't see how you using bad software makes this any less a configuration problem on your end.
My intention here was to say that the fact that the 'rad' software fails to advertise prefixes with a zero lifetime is sad. That's like basic, essential functionality and it's always sad when software fails to implement basic, essential functionality.
My intention was NOT to assert that your configuration (or -worse- you, yourself) was sad or whatever.
> ...now you’re saying I’m using “bad software” for using the built-in, recommended router advertisement daemon...
Yes? It's possible for the recommended thing to be bad software. If you haven't discovered this, you DEFINITELY will as time goes on.
That's a configuration problem on your end. Your border router needs to notice that it's being instructed to switch delegated prefixes and instruct radvd (or whatever route advertising daemon it's using) to advertise the now-defunct prefixes with a zero lifetime just before or just as you're advertising the new prefixes.
With this information, devices on your LAN that aren't asleep will do the right thing, and devices that were asleep should reconfigure their network interfaces when they wake up... assuming that the world hasn't changed while they've been asleep is something only morons would do (coughAppleComputerscough).