

With regards to the backup key, Yubikey recommends to save (screenshot) the QR code that is generated during 2FA setup to setup the backup key later on. Maybe that is also a workaround for services that only allow a single 2FA device. https://support.yubico.com/hc/en-us/articles/360021919459-How-to-register-your-spare-key
Just looking back at my purchase history, I got my Yubikey’s back in January 2020, it appears that I never read this doc about scanning the QR code for the backup key, or maybe I did? I don’t really remember it all too well. Regardless In certain circumstances my keys do the exact same thing and I’m quite sure I followed some guide to create one primary and one secondary key but it’s possible that guide has gone outdated.
Similar to something like Keepass, the database is local and you are in charge of making backups and such.
I can totally respect the folks who opted to self host, I’m horrible when it comes to backing up data and such and self hosting wasn’t really my thing back in 2020 so it never really was on my radar.
In the end this comes always down to an optimization problem between security and convenience that everyone has to decided for themself.
Couldn’t agree with you more, everybody has that dial between convenience and security and should adjust accordingly.
There are many ways, a popular choice would be managing your own recursive DNS resolver and then blocking the endpoint it contacts.
PiHole - Non recursive but offers blocking capabilities, can make it recursive with Unbound.
Technitium - Recursive but not nearly as user friendly as PiHole, also lacks the fancy Ui.