Unable to use custom PDS to log in

[midnightdoggo19]

When attempting to log in to the site, I'm unable to use accounts registered on my custom PDS. Using the browser's inspect tool, it seems like the error occurs because the site makes an API call to:
"https://bsky.social/xrpc/com.atproto.identity.resolveHandle?handle=example.user.handle"
It does this even if that's not where the account's data is located (which is what happens if the account is linked to another PDS). "bsky.social" doesn't have the requested information and therefore returns an error, stating that the request is invalid. In fact, it's the same error you'd get from clicking that example link above; bsky.social doesn't have the user saved and returns an error. However, if the site were to query:
"https://correct.pds.com/xrpc/com.atproto.identity.resolveHandle?handle=example.user.handle" (the location of the account)
It'd get the response it was looking for. I've verified this by visiting the corresponding URLs in my browser and I've gotten the correct response with the account DID only on the custom PDS' URL (in my tests, I was using real accounts on a real PDS).

A possible solution for this problem is to simply ask the user which PDS they'd like to use, with the default of course being "bsky.social".