Preface, I'm not a Debian developer.
You're not the only one, but after some tinkering I've discovered that there's a whole slew of "Hockeypuck" GPG/PGP servers that seem to work fine for me.
They all seem to intercommunicate reliably. I was able to issue a revocation for an old key to pgpkeys.eu and it populated across to pgp.id within minutes.
I posted on Mastodon about this and somebody sent me this link with a list of various compatible servers. I haven't tried them all, just thought I'd share.
On Mon, 2025-11-17 at 18:32 +0100, Francesco Poli - invernomuto at paranoici.org wrote:
On Mon, 17 Nov 2025 10:49:00 -0500 Jeffrey Walton wrote:
[...]
Daniel Kahn Gillmor (dkg) recommends using a constrained keyserver
like keys.openpgp.org if you want to check for certificate updates,
revocation, expiration, or subkey rollover.
Dear Jeffrey, thanks for following up.
I've just tried to refresh 50 keys with:
keyserver hkps://keys.openpgp.org
in my ~/.gnupg/gpg.conf
It only found 2 of them and exited with non-zero status, spitting out
out the following error message:
gpg: keyserver refresh failed: No data
Am I the only one who's experiencing issues in refreshing OpenPGP keys
with gnupg/2.4.8-4 on an up-to-date Debian testing box?
Am I the only one left who still uses gnupg in Debian? Have you all
switched to sequoia-chameleon-gnupg, perhaps?
I am really puzzled... :-(