What problem does it solve? Serving an Internet Computer canister under your own domain requires coordinating DNS records, a domain ownership file, and a registration REST API, and small misconfigurations silently break TLS provisioning or canister calls. ## Core Features & Use Cases - DNS Configuration Guidance: Provides the exact CNAME, TXT, and ACME challenge records needed, including apex-domain workarounds with ANAME/ALIAS records. - Registration Lifecycle Management: Covers validate, register, update, and delete operations against the icp.net/custom-domains/v1 REST API with curl commands and expected JSON responses. - Troubleshooting Playbook: Lists nine common failure modes such as stale ACME TXT records, duplicate _canister-id entries, and misconfigured HttpAgent hosts, each with a concrete fix. - Use Case: You deployed a React frontend canister and want it reachable at app.example.com with a valid TLS certificate while keeping Internet Identity principals stable across origins. ## Quick Start Ask the assistant to walk you through registering your custom domain for your deployed IC canister, starting with the DNS records and the .well-known/ic-domains file.
