resolveHandle returning old did in bsky.social's PDS

[samuelgoto]

I started running my own PDS for my handle @sgo.to (code here based on this), which I think I've done successfully (here https://pds.sgo.to).

I didn't go through a migration (because I didn't mind losing my posts/followers), and I figured I could just generate a new DID.

It seems, however, that I can no longer login to https://bsky.app/profile/sgo.to with my PDS: it says that I have an invalid handle now.

My TXT DNS records seem correct:

dig -t txt _atproto.sgo.to | grep did              
_atproto.sgo.to.	21600	IN	TXT	"did:plc:blnjevhuoo7j3awhxajd7a2o"

which return the same DID in my PDS:

curl \
  --silent \
  --show-error \
  --request GET \ 
  "http://pds.sgo.to/xrpc/com.atproto.identity.resolveHandle?handle=sgo.to"
{"did":"did:plc:blnjevhuoo7j3awhxajd7a2o"}% 

which also seems to be published correctly to the directory:

curl -s "https://plc.directory/did:plc:blnjevhuoo7j3awhxajd7a2o" | jq .
{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/multikey/v1",
    "https://w3id.org/security/suites/secp256k1-2019/v1"
  ],
  "id": "did:plc:blnjevhuoo7j3awhxajd7a2o",
  "alsoKnownAs": [
    "at://sgo.to"
  ],
  "verificationMethod": [
    {
      "id": "did:plc:blnjevhuoo7j3awhxajd7a2o#atproto",
      "type": "Multikey",
      "controller": "did:plc:blnjevhuoo7j3awhxajd7a2o",
      "publicKeyMultibase": "zQ3shjK6FQoaYCjUUt5czfrYf7MMJchS5RHajDU4y11bWYQQX"
    }
  ],
  "service": [
    {
      "id": "#atproto_pds",
      "type": "AtprotoPersonalDataServer",
      "serviceEndpoint": "https://pds.sgo.to"
    }
  ]
}

However, the bluesky.social PDS is still resolving the handle incorrectly here:

curl \                                         
  --silent \
  --show-error \
  --request GET \
  "https://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle=sgo.to"
{"did":"did:plc:bftbdgcbe4zclvpkboe4hleq"}% 

Which I'm guessing is why the web view things my handle is invalid ...

Is this some caching invalidation that I need to perform in the bluesky PDS to say that @sgo.to no longer should point to did:plc:bftbdgcbe4zclvpkboe4hleq but rather to did:plc:blnjevhuoo7j3awhxajd7a2o instead? Or maybe that's just my DNS server that is taking a while to propagate my TXT record with my new DID?

The at browser seems to say that the handle is invalid too:

https://atproto-browser.vercel.app/at/did:plc:blnjevhuoo7j3awhxajd7a2o

But it does seem like I managed to create posts in my PDS using the bluesky app view:

https://atproto-browser.vercel.app/at/did:plc:blnjevhuoo7j3awhxajd7a2o/app.bsky.feed.post/3lf7jamjdt22q