Custom domain on GoDaddy
GoDaddy’s DNS editor lives under My Products. Its Name field is strictly relative — enter only the part left of your domain, never the full hostname.
The records you’ll create
Your exact names and values are generated on the server’s Deployments tab → Custom domain card. They follow this shape:
| Type | Name | Value | Purpose |
|---|---|---|---|
| CNAME | mcp.acme.com | connect.mcp-dns.com | Routes traffic to MCPCloud |
| TXT | _cf-custom-hostname.mcp.acme.com | ce2337e3-…-c789c237d377 | Proves you own the domain |
Setup on GoDaddy
- Sign in at godaddy.com, open My Products, and click DNS next to the domain.
- Add a CNAME record: Name is the subdomain only (e.g. `mcp`), Value is the CNAME target from your MCPCloud domain card. Keep TTL at the shortest option offered (usually ½ hour or 600 seconds).
- Add a TXT record: Name is the ownership labels without your domain (e.g. `_cf-custom-hostname.mcp`), Value is the token from the card.
- Save both, then hit Recheck in MCPCloud. GoDaddy propagation typically takes a few minutes but can stretch to the TTL you chose.
Verify and go live
Back on the Custom domain card, hit Recheck. The status walks from Verifying DNS to Issuing certificate to Active — usually within minutes of the records propagating. Once Active, your server answers at https://mcp.acme.com/mcp and the certificate renews automatically.
Troubleshooting
Verification stays pending for a long time.
GoDaddy defaults TTL to 1 hour — earlier wrong attempts can be cached that long. Confirm the records with a checker like dnschecker.org, and lower the TTL for faster edits.
GoDaddy rejects the TXT name.
Remove your domain from the end of the name — GoDaddy appends it automatically. `_cf-custom-hostname.mcp` is correct; the fully-qualified form is not.
Calls through the custom domain get a 403 (often “browser_signature_banned” or a challenge page) while the platform URL works.
Your DNS zone’s WAF or bot-protection rules apply to the custom hostname, and MCP clients send unusual or minimal user agents. Exempt the hostname (or the path) from bot fight / managed challenge rules in your zone, or point clients at the platform URL until you do. The 403 comes from your zone, not from MCPCloud.
Other DNS providers