On Fri, Jan 31, 2025 at 10:28:42AM +0100, Libor Peltan wrote:
> Hi,
>
> On 31. 01. 25 10:18, Daniel Gröber wrote:
> > now I redeploy the primary (after, say, the machine goes up in
> > flames). For a short while there secondaries will see the dummy zone's
> > serial. IF I'm unlucky and the serial-math works out
>
> Do you think that you make 2000000000+ updates to some zone? It is 23 days
> of 1000 upd/sec torture.
Who's to say. I learned yesterday some people stream video over DNS :D
$ dig +short TXT {0..92}.vid.demo.servfail.network | sed 's/[" ]*//g' |
base64 -d | mpv -
Seriously though. It is unlikely, but it's just one of those nagging things
I don't want to have in the back of my mind and/or communicate if I
recommend this setup to people. Keep in mind it's not so much about what
I'm going to do with this, but what other people might come up with once I
publish it.
I'm ofc. happy to send patches if y'all are to busy to enable this niche
use-case.
> And even if, than if you configure journal-content:all on the secondary/ies,
> they should have overview about all the history and don't mess up if the
> primary goes backwards in SOA serials.
How do you mean? I'm not aware of this behaviour, is that documented
somewhere?
Thanks,
--Daniel
--
