bluesky-custom-domain-handlelisted
Install: claude install-skill postoncehq/bluesky-mcp
# Bluesky custom domain handle
This is an advisory walkthrough. The user makes every change in their DNS provider or web host and in the Bluesky app; the PostOnce MCP doesn't change handles or DNS. Never ask for DNS, registrar or Bluesky passwords.
## Before starting
Get: the domain or subdomain they want (`name.com`, or `name.company.com` for a team member), where its DNS is managed (Cloudflare, Namecheap, Squarespace, GoDaddy, Route 53 and so on), and whether they can edit DNS or only upload files to the site. A subdomain works well for staff handles on a company domain.
## Step 1: get the DID from Bluesky
In the Bluesky app: **Settings → Account → Handle → I have my own domain**. Enter the domain. Bluesky shows the exact record to add, containing the account's DID (it looks like `did:plc:` followed by letters and numbers). Always copy the value Bluesky shows; don't type it from memory.
## Step 2, option A: DNS TXT record (recommended)
Add a TXT record in the DNS provider:
| Field | Value |
| --- | --- |
| Type | TXT |
| Host / Name | `_atproto` (for a subdomain handle: `_atproto.name`) |
| Value | `did=did:plc:...` exactly as Bluesky shows it |
| TTL | Default |
Notes:
- Some providers add the domain automatically; if the host field shows `_atproto.name.com.name.com` after saving, enter only `_atproto`.
- Remove any older `_atproto` TXT record for the same name; there must be only one.
- DNS changes can take minutes to hours. `dig TXT _atproto.name.com` (or an onl