When you try to set a custom domain as your Bluesky handle, you may see the error message “Domain already in use.” This happens when the same domain is already linked to another Bluesky account. Bluesky requires each domain to be used by only one account at a time. This article explains why the error occurs and provides step-by-step instructions to fix it.
The error is caused by the domain being registered to a different Bluesky account, either your own previous account or someone else’s. You might have changed your handle in the past, or you may be trying to use a domain that another user already claimed. The fix involves removing the domain from the old account or using a subdomain for a new account.
Below you will find the exact steps to resolve the conflict. You will also learn how to prevent this error in the future.
Key Takeaways: Resolving the Bluesky Domain Already in Use Error
- Settings > Account > Handle: Check which account currently owns the domain by viewing the handle settings.
- DNS TXT Record: Verify the domain ownership by adding or checking the DNS TXT record provided by Bluesky.
- Remove domain from old account: Either change the old account’s handle or delete the account to free the domain for a new account.
Why the Domain Already in Use Error Occurs
Bluesky associates each custom domain with exactly one account. When you attempt to set a domain as your handle, Bluesky checks its database to see if that domain is already linked to another account. If a match is found, the system displays the “Domain already in use” error and blocks the change.
The most common causes are:
- Previous account ownership: You or someone else previously set the domain as a handle on a different Bluesky account. Even if the account is inactive or deleted, the domain may still be locked.
- Multiple accounts with same domain: You tried to use the same domain for two separate Bluesky accounts. This is not allowed.
- Domain transfer without cleanup: You changed your handle from a custom domain to a default handle but did not remove the domain from the old account first.
Bluesky uses DNS TXT records to verify domain ownership. However, the verification only proves you control the domain. It does not override the one-account-per-domain rule. Even after successful DNS verification, the error can appear if the domain is already registered on Bluesky’s side.
Steps to Resolve the Domain Already in Use Error
Follow these steps in order. Each step covers a different scenario. Start with step one and proceed until the error is resolved.
- Check which account owns the domain
Open Bluesky on your desktop browser. Go to Settings > Account > Handle. If you see the domain listed there, your current account owns it. If you see a different handle, the domain is linked to another account you may have forgotten. Try logging into that account using the domain as a login hint. If you cannot remember the account, proceed to step two. - Remove the domain from the old Bluesky account
Log into the account that currently has the domain as its handle. Go to Settings > Account > Handle. Click Change Handle and select a default Bluesky handle (for example, @username.bsky.social). Save the change. This frees the domain. Now log out and log into the account where you want to use the domain. Set the domain as your handle again. - Delete the old account if you cannot change its handle
If you cannot log into the old account or change its handle, you must delete it. Go to Settings > Account > Delete Account. Confirm the deletion. Wait for the deletion to process (usually a few minutes). Then log into your desired account and set the domain as your handle. Note: Deleting an account is permanent and removes all posts and data. - Use a subdomain instead
If the main domain is permanently locked to another user or you cannot delete the old account, use a subdomain. For example, if example.com is taken, use handle.example.com or blog.example.com. Go to your DNS provider and add a TXT record for the subdomain. Then set the subdomain as your Bluesky handle. This bypasses the conflict because subdomains are treated as separate domains.
If Bluesky Still Shows the Error After the Fix
In some cases, the error persists even after you have removed the domain from the old account. This can happen due to caching or propagation delays. Try the following solutions.
DNS Propagation Delay
Bluesky checks DNS records periodically. After you change your handle or delete an account, wait up to 30 minutes. Then refresh the Bluesky page and try again. You can also clear your browser DNS cache by running ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS.
Bluesky Server Cache
Bluesky caches domain ownership data for performance. If the error persists, log out of all devices, wait 15 minutes, and log back in. Then attempt to set the domain again. If the issue continues, contact Bluesky support through the app or their help site.
Multiple TXT Records Conflict
If you have multiple TXT records for the same domain, Bluesky may read the wrong one. Ensure you have only one TXT record with the exact value Bluesky provided. Remove any old or duplicate records. Wait for DNS propagation, then retry.
| Item | Using main domain | Using subdomain |
|---|---|---|
| Description | Use the root domain (example.com) as your handle | Use a subdomain (handle.example.com) as your handle |
| Conflict risk | High if domain was used before | Low, each subdomain is unique |
| DNS setup | One TXT record for the root domain | One TXT record for the subdomain |
| Best for | New domains never used on Bluesky | Domains already taken by another account |
This table compares the two approaches. Use the subdomain method if the main domain is permanently locked.
You can now resolve the Bluesky “Domain already in use” error by removing the domain from the old account or using a subdomain. Always check which account owns the domain before attempting to set it. To avoid future conflicts, keep a record of which Bluesky account uses each custom domain. If you manage multiple accounts, use unique subdomains for each one from the start.