You changed your Bluesky handle, but after a few hours or days it reverted back to the old one. This problem happens when the handle change does not fully propagate through Bluesky’s distributed network or when a custom domain handle fails to verify. The root cause is almost always an incomplete DNS configuration or a caching delay in the AT Protocol. This article explains why handles revert on Bluesky and provides the exact steps to fix a handle that keeps switching back.
Key Takeaways: Stopping Handle Reversion on Bluesky
- Settings > Account > Handle: Change your handle here and confirm with your password
- DNS TXT record for custom domains: Add the correct AT Protocol verification string to stop reverts
- Clear browser cache and app data: Forces the client to fetch the updated handle from the relay
Why a Bluesky Handle Reverts to the Previous Handle
Bluesky uses the AT Protocol, which separates account identity from the hosting server. Your handle is a public alias that is mapped to your Decentralized Identifier or DID. When you change your handle, the Bluesky relay must update this mapping. If the update does not complete, the relay serves the old handle to all clients.
For standard handles ending in bsky.social, reverts are rare but can happen if you edit the handle field too quickly or if your session token expires during the change. For custom domain handles such as @yourname.com, reverts are much more common. The domain owner must add a DNS TXT record that contains the AT Protocol verification string. If this record is missing, incorrect, or not propagated, Bluesky cannot confirm that you own the domain. After a few hours, the system falls back to the previous handle.
Another cause is client-side caching. The Bluesky app or web client may store the old handle locally. Even after the server side is correct, the stale cache makes the handle appear reverted in your interface.
Steps to Fix a Bluesky Handle That Keeps Reverting
Follow these steps in order. Each step addresses a specific cause of handle reversion.
- Change the handle again in Settings
Open Bluesky and go to Settings > Account > Handle. Type your desired handle. If you use a custom domain, enter the full domain such as yourname.com without the @ symbol. Tap Save or press Enter. Enter your account password when prompted. Wait at least 30 seconds before closing the settings page. - Verify the DNS TXT record for custom domains
If you use a custom domain, log in to your domain registrar or DNS hosting provider. Navigate to the DNS settings for your domain. Add a new TXT record with the host field set to _atproto and the value set to the verification string provided by Bluesky. The string looks like did=did:plc:abc123def456. Wait for DNS propagation, which can take from a few minutes to 48 hours. Use a tool like whatsmydns.net to check if the TXT record is visible globally. - Clear the Bluesky app cache
On the Bluesky mobile app, go to Settings > Moderation > Cached media and tap Clear all cached media. On the web client, open your browser settings, find Clear browsing data, and select Cached images and files. Do not clear cookies or site data unless you want to sign in again. After clearing, reload the Bluesky tab. - Sign out and sign back in
Go to Settings > Account > Sign out. Close the app or browser tab completely. Open Bluesky again and sign in with your email and password. This forces the client to download the latest handle mapping from the relay. - Wait for relay propagation
After changing a handle, Bluesky relays can take up to one hour to update. If you changed the handle again in step 1, wait at least one hour before checking. Do not change the handle again during this waiting period. Changing it repeatedly resets the propagation timer.
If Bluesky Still Reverts the Handle After the Main Fix
Custom domain handle still reverts after DNS record is added
The DNS TXT record may have a typo or an incorrect DID value. Go back to your DNS provider and copy the exact verification string from Bluesky Settings > Account > Handle > Add custom domain. The string must match exactly, including the did= prefix. Also confirm that your domain registrar is not overriding the TXT record with a default record. Remove any old TXT records that reference a previous Bluesky handle.
Handle reverts only on one device
This is almost always a caching issue on that specific device. On iOS, go to Settings > Safari > Advanced > Website Data and swipe to delete Bluesky data. On Android, go to Settings > Apps > Bluesky > Storage and tap Clear cache. On desktop browsers, open Developer Tools F12, go to the Application tab, select Clear storage, and click Clear site data. Then reload Bluesky.
Handle reverts after a few days
Your session token may have expired, and the client cannot re-verify the handle. Sign out completely and sign back in. If the problem persists, revoke all active sessions in Settings > Account > App Passwords. Then sign in again and change the handle one more time.
Bluesky Handle Types: Standard vs Custom Domain
| Item | Standard Handle | Custom Domain Handle |
|---|---|---|
| Format | @username.bsky.social | @yourname.com |
| Setup time | Instant | Up to 48 hours for DNS propagation |
| DNS record required | None | TXT record for _atproto |
| Revert risk | Low | High if DNS is misconfigured |
| Revert fix | Clear cache and sign out | Fix DNS record and clear cache |
This table shows that custom domain handles require more maintenance but offer full brand control. Standard handles are simpler but cannot be moved to another server.
You can now fix a Bluesky handle that keeps reverting by clearing your cache, verifying your DNS record, and waiting for relay propagation. If you use a custom domain, double-check the TXT record at _atproto.yourname.com using a DNS lookup tool. For a permanent solution on custom domains, enable DNSSEC at your registrar to prevent DNS spoofing that can interfere with handle verification.