Option to bypass caching with resolveHandle?

[DavidBuchanan314]

When changing handle to a custom domain in bsky.app (and presumably others too), the client issues a resolveHandle before allowing the user to proceed to updateHandle.

If the user has only recently updated their DNS records, there's a good chance their first resolveHandle will fail - and that failure response will be cached (or maybe they made a mistake in configuring their DNS record the first time - now that mistake is cached). Now the user has to wait for the cache to expire before they can try again. This is doubly confusing to troubleshoot because there's (usually) caching at the DNS level, too.

(note: I don't know how the handle caching is implemented in the reference PDS/relay/appview implementation, I'm thinking about the general case here)

For these situations where an updated handle is expected, it would help if the client could pass a noCache=true parameter (or similar) to hint to the PDS that it should bypass its cache for this request. The PDS can make this an authed-only option and/or rate limit it as appropriate.

I think this would reduce the incidence of "it won't let me update my handle" issues, and maybe also allow the PDS to cache handles for longer by default.