What a parking page tells you

Registering a domain gives you control over its name, but it does not automatically create a website. Until you connect the domain to a hosting service, your registrar may display a default page. It might say the domain is parked, show a placeholder, or offer a simple site-building prompt. This generally means a web request reached a service that has a default response for the domain; it does not, by itself, mean anything is wrong with your registration.

The page can also appear after you have built a site. Your domain may still point to the registrar’s default service, your hosting account may not recognize the domain yet, or your browser may be showing a cached result. The useful question is not just “Where is my website?” but “Which service currently receives requests for this domain, and is it ready to serve my site?”

Find out who controls your DNS

Start in your registrar account and find the domain’s nameserver settings. Nameservers identify the provider that manages the domain’s DNS records. The registrar may manage those records, or you may have delegated DNS to your web host or another provider. Make DNS changes wherever the active nameservers point; editing a record in an inactive DNS panel will not change where visitors go.

Next, look at the instructions from your chosen hosting service. Hosts commonly ask you either to change nameservers or to keep your current nameservers and edit specific DNS records. Treat these as alternative setup paths unless your host explicitly says otherwise. Before changing nameservers, note your existing records, especially those used for email. Replacing the entire DNS setup without carrying over needed records can interrupt services unrelated to your website.

Connect the domain to your site

First, add the domain to your hosting account or website builder and make sure the site is published there. A correct DNS record cannot display a site that the host has not associated with your domain. Your host should provide the exact destination to use, such as an IP address for an A record or a hostname for a CNAME record. Copy that destination from your account rather than guessing it.

Then update the web records in the active DNS zone. The root domain, sometimes shown as @, and the www subdomain may need separate entries. A common arrangement points the root to the host with an A record and points www to a hostname with a CNAME record, but follow your host’s instructions: DNS providers and hosting platforms support different arrangements. Remove or replace conflicting parking records for the same names, while leaving unrelated records alone.

DNS pointing and web forwarding are not the same thing. DNS records direct a name toward a service; forwarding sends visitors from one web address to another. If you want both example.com and www.example.com to work, configure both with your host and choose a preferred address if the host offers redirects. Once the site loads, check that HTTPS works for each address you intend to use. Your host may need to finish setting up a certificate after the domain is connected.

If the parking page still appears

DNS changes are not always visible everywhere at once. Resolvers can temporarily reuse cached answers, so an old parking destination may persist while the updated record becomes available. Check the domain in a private browser window or on another network to help distinguish a local cache from a broader configuration issue. Avoid repeatedly changing records while waiting; first confirm that the active DNS zone contains the values your host requested.

If the page persists, work through the path in order: verify the nameservers, inspect the root and www records, and confirm that both versions of the domain are added to the hosting account. If only one version works, the other may lack a record or a host-side setting. If the correct host receives the request but shows its own default page, the remaining issue may be site publishing or domain assignment rather than DNS.

Protect the rest of your domain setup

A website change should not require deleting every DNS record. MX records route incoming email, while TXT and other records may support email authentication or ownership checks. Keep a copy of the existing zone before making broad changes, and compare it with the new provider’s setup instructions. If you must switch nameservers, recreate required non-website records in the new DNS zone before relying on it.

Use your account’s normal security features, such as a strong unique password and multifactor authentication when available. Share only the DNS values a support team needs to diagnose a problem, not your login credentials or recovery codes. Once your site and email work as expected, remove obsolete parking records so the domain’s configuration is easier to understand the next time you make a change.

Back to category ↗