2 min readAn original planning guide. Use the linked primary documentation for platform details and the supported procedure for your environment.
Collect the exact instructions
Use the destination service's current hostname, record type, and value requirements. Avoid reusing values from an unrelated account or old guide.
Check existing dependencies
Review records at the affected name and separate website routing from email and domain-verification records.
Verify configuration and resolution
Confirm the service accepts the domain and that authoritative DNS returns the expected records. Account for cached earlier answers.
Open the public hostname
Check the intended HTTPS address, certificate hostname, and content. Test both apex and www if both are meant to work.
Worked scenario
See the plan in practice.
A service accepts www.example.com while the business card prints example.com. Include the public address people will use in acceptance checks.
Review your result
Your acceptance checklist
Instructions current- Dependencies preserved
- HTTPS checked
Use these checks to identify gaps in your domain-connection verification checklist. Assign an owner to any unresolved item before the next dependent step.
The terms behind the task
Primary references
For the underlying concepts and current platform details:
