Choose whether you need a temporary holding page, a domain-sale page or an HTTP redirect. Confirm the service is included or separately activated. Record existing website and mail DNS so parking changes do not unintentionally interrupt email.

1. Add the domain to the chosen parking or hosting service and follow any ownership verification. Use an account you control, not an arbitrary public server address.
2. Obtain the exact DNS records or nameservers required by that service. Prefer changing only website records when mail and other DNS should remain with the current provider.
3. If a complete nameserver change is required, recreate the necessary mail, verification and other records at the destination before changing delegation.
4. Configure the page content or redirect destination and arrange a certificate for each hostname visitors will use. Include both apex and www if both should work.
5. Publish the DNS change and test the intended holding page, destination or contact link. Keep the original service ready if a controlled reversal is needed.

Open the domain from an independent connection after checking authoritative DNS. Verify that the page belongs to your account, the certificate is valid and mail records remain correct.

A default server page can mean the DNS reaches a server that has not been configured for your hostname. A stale parking page can mean cached DNS or an old CDN/application cache. Identify the responding layer before moving nameservers again.

• Make www and the root domain reach the same website consistently
• Point an apex domain at a hosted service without an invalid CNAME
• Add a provider's DNS verification record and remove it only when appropriate
• Prepare a reversible DNS change with an exact before-and-after record list
• Understand when a wildcard DNS record does and does not apply

• Nabtech: web hosting
• RFC 1034