You bought a domain name. You signed up for web hosting. Now you need to connect the two so that typing your domain into a browser actually loads your website.
This is one of the most confusing parts of getting a website online because domain registration, DNS, and web hosting are often handled in different places. The good news is that the connection itself is usually straightforward once you know which settings matter.
At The Hosting Hotel, our preference is that members rarely need to think about DNS at all. If you're launching a new site with us, we handle the connection between the domain, hosting, and email as part of onboarding. This guide explains what is happening behind the scenes for anyone who wants to understand it or is managing the setup themselves.
How a domain name connects to web hosting
Your domain name and your web hosting account perform different jobs.
Your domain registrar is the company where your domain name is registered. It controls important settings that determine where the domain points.
Your web hosting provider stores your website files on a server and makes them available on the internet.
A third service may also be involved: your DNS provider. DNS is the system that tells browsers, email servers, and other services where to find the different parts of your domain. Sometimes your registrar manages DNS. Sometimes your hosting provider does. Some businesses use a separate DNS provider.
The exact dashboard you use will vary, but the underlying process is the same. You are telling DNS where your website lives.
If web hosting terminology is still unfamiliar, our plain-English guide to how web hosting works explains the basic pieces first.
What DNS does in plain English
DNS stands for Domain Name System. It translates easy-to-remember domain names into the technical addresses computers use to find services on the internet.
When someone enters your domain in a browser, DNS tells the browser which server should receive that request.
Your website may use one set of DNS records, while your email and other services use different records. That is why changing DNS should be done carefully when a domain is already in use.
Before changing anything, check where your DNS is managed
Before you connect your domain to hosting, find out which service currently manages your DNS.
In your domain registrar account, look for a section with a name such as:
- DNS
- Nameservers
- DNS Management
- Advanced DNS
- Domain Management
The labels vary by provider, but you are looking for either a list of nameservers or a DNS zone containing records such as A, CNAME, MX, and TXT.
Protect your existing email before changing nameservers
This is especially important if your business already uses email addresses on the domain.
Changing nameservers moves responsibility for the entire DNS zone to a different provider. If your existing email records are not recreated there, your email can stop working even though the website is configured correctly.
Before changing nameservers, make sure you know whether the domain already has:
- MX records for email delivery
- SPF, DKIM, or DMARC records
- TXT records used for verification
- Records for other business services
- Subdomains pointing to other systems
Before changing anything, make a record of the DNS settings that already exist. One of the easiest mistakes to make during a migration is changing nameservers without first noting what was there before. A screenshot or exported copy gives you something to compare against if a service stops working afterward.
Should you change DNS settings yourself?
If you do not know what the existing records do, how they relate to each other, or which services depend on them, it is usually better not to change them blindly. A small DNS change can affect more than the website. It can also interrupt email, verification records, subdomains, or other business services.
At The Hosting Hotel, we handle this part for members because we do not think understanding DNS should be a requirement for having a website. Ideally, a business owner should be able to choose a domain, launch a site, and get back to running the business without ever needing to learn what a nameserver is.
For email, first determine whether the mailbox is local to the current hosting environment or remote, such as email hosted by a separate provider. Remote email usually depends on DNS records that must remain intact even when the website moves.
Choose how you want to connect the domain
There are two common ways to connect a domain name to web hosting.
The right method depends on who you want managing DNS after the change.
Option 1: Change the nameservers
Changing nameservers tells your registrar that another provider should manage the domain's DNS.
At The Hosting Hotel, when a member already owns a domain elsewhere, our first preference is usually to transfer the domain into our management, and we offer to cover the transfer fee. That lets the domain, nameservers, and DNS stay together instead of being split across several providers.
If the member prefers to keep the domain registered where it is, we generally prefer to update the nameservers so DNS can still be managed from the hosting dashboards we provide. The goal is not to move things around for the sake of it. It is to reduce the number of places someone has to remember when something eventually needs to be changed.
This can be the simplest option when:
- You are setting up a new domain
- Your hosting provider is supposed to manage DNS
- You do not have existing services that need to remain at the current DNS provider
- Your provider has given you nameserver addresses to use
Nameserver addresses often look something like:
ns1.examplehost.com
ns2.examplehost.com
Once those nameservers are active, DNS records for the website, email, and other services are managed wherever those nameservers point.
Option 2: Keep the current nameservers and update DNS records
Instead of moving the entire DNS zone, you can leave the existing nameservers in place and change only the records that control the website.
This is often the better approach when:
- Your email is already configured and working
- A separate DNS service manages your domain
- Other applications depend on existing DNS records
- You only want to move the website
In this case, your hosting provider will usually give you an IP address or hostname to use for the website. You then update the appropriate A and CNAME records at your current DNS provider.
How to connect your domain by changing nameservers
If your hosting provider is going to manage DNS, the process is usually straightforward.
Step 1: Get the nameservers from your hosting provider
- Log in to your hosting account or check the setup information you received when the account was created.
- Look for the nameservers assigned to your hosting account. Most providers give you at least two.
- Copy them exactly. A typo can prevent your domain from resolving correctly.
Step 2: Open the nameserver settings at your registrar
- Log in to the company where your domain is registered.
- Open the domain you want to connect and find its nameserver settings. You may see options such as default nameservers, provider DNS, or custom nameservers.
- Choose the option that lets you enter custom nameservers.
Step 3: Replace the existing nameservers
- Enter the nameservers supplied by your hosting provider and save the change.
- Once saved, DNS servers across the internet will gradually begin using the new nameservers. This process is commonly called DNS propagation.
Step 4: Confirm the DNS zone at the new provider
- After changing nameservers, make sure the new DNS provider has the records your domain needs.
- For a new website, this may already be configured automatically. If the domain also uses professional email or other services, confirm that those records exist at the new provider before relying on the new DNS setup.
How to connect your domain using DNS records
If you want to keep your current DNS provider, you will normally update the records that control website traffic.
Your hosting provider should tell you exactly which destination to use. Follow their values rather than guessing.
Update the A record for the root domain
An A record points a domain or subdomain to an IPv4 address.
For the main domain, the host field is often shown as @, although some DNS providers display the root domain differently.
A typical configuration might look like:
Host: @
Type: A
Value: the IP address supplied by your hosting provider
TTL: provider default
If an A record already exists for the root domain, edit it rather than creating conflicting records unless your hosting provider specifically tells you otherwise.
Configure the www version
Most businesses also want www.yourdomain.ca to reach the same website as yourdomain.ca.
This is commonly handled with a CNAME record for www, pointing it to the main domain or to another hostname supplied by the hosting provider.
Your hosting platform may configure this differently, so use the destination it provides.
After the DNS records are correct, your website should be configured to recognize both versions of the domain and redirect visitors to the preferred version.
Leave email records alone unless you are moving email
If your email is already working and you are only moving the website, avoid changing MX records and email-related TXT records.
Those records often control:
- Where incoming email is delivered
- Whether other mail servers trust messages from your domain
- Domain verification for email services
- Protection against domain spoofing
Changing only the website-related records lets you move the website without unnecessarily disrupting email.
What DNS propagation actually means
DNS changes do not always appear instantly. Other DNS servers may continue using a previously cached answer until it expires and they request the updated information.
That delay is what people mean by DNS propagation.
How long DNS changes can take
Changes to individual records such as A or CNAME records are often visible within minutes or a few hours, although timing depends on the previous record's TTL and caching.
Nameserver changes can take longer. Several hours is common, and it can sometimes take 24 to 48 hours for the change to be reflected widely.
During that period, one person may see the new website while another still reaches the old server. That does not automatically mean something is broken.
Lower the TTL before a planned migration
If you are moving an existing website and have access to the current DNS zone, you can reduce the TTL on the records you plan to change before the migration.
Doing this roughly 24 to 48 hours before the switch gives older cached records time to expire. A lower TTL, such as 300 seconds, can help DNS resolvers refresh more quickly after the final change. This is one of the simple steps we use during planned migrations because it can make the transition noticeably faster and reduce the period where different visitors may reach different servers.
Once the migration is stable, the TTL can be returned to a more typical value.
This step is optional and is most useful when minimizing disruption during a planned website migration.
How to check whether your domain is connected
After making the change, test the domain from more than one place.
You can:
- Open the domain in your browser
- Test both the root domain and the www version
- Try a second network, such as mobile data
- Use a DNS lookup or propagation-checking service
- Confirm the domain resolves to the IP address or hostname expected by your hosting provider
If you are moving an existing website, keep the old hosting account active until the new site has been resolving reliably for at least 24 to 48 hours. That gives cached DNS records time to expire and reduces the chance that some visitors are sent to a server that has already been shut down.
What to do if the domain is not connecting
Most connection problems come down to a small number of configuration issues.
The old website or a placeholder page still appears
If you recently changed DNS, cached records may still be pointing you to the previous server.
Give the change some time, try another network, and check the current DNS results. Clearing your browser cache may help if the browser itself is holding onto an old page, but browser caching and DNS caching are separate things.
If the old destination continues to appear well after the expected propagation window, verify the nameservers or DNS records.
The root domain works but www does not
Check the DNS record for www and confirm that your hosting account is configured to accept that version of the domain.
The reverse can also happen if the root-domain A record is missing or incorrect.
Both versions should be configured even if your website ultimately redirects visitors to only one of them.
The website works but email stops
This often happens after nameservers are changed without recreating the existing email records at the new DNS provider.
Check the MX records first, then verify any SPF, DKIM, DMARC, and other TXT records required by your email service.
If you are unsure which records are missing, contact your email provider before making further changes.
The domain still does not resolve after the expected propagation period
If the domain is still not resolving correctly after roughly 48 hours, it is worth checking the configuration rather than continuing to wait.
Look for:
- Misspelled nameservers
- An incorrect server IP address
- Duplicate or conflicting DNS records
- Missing DNS records at the new provider
- A domain that has not been added to the hosting account
- DNSSEC settings that no longer match the active DNS provider
Your hosting provider should be able to help identify which part of the connection is failing.
Connecting a domain should be a one-time setup
Once the domain is correctly connected to your hosting account, you generally do not need to think about these settings again unless you move the website, change DNS providers, or reconfigure another service on the domain.
The key is deciding who should manage DNS before you make the change. If your hosting provider should manage everything, changing nameservers can keep the setup simple. If your domain already has working email or other services, keeping the existing DNS provider and updating only the website records may reduce unnecessary disruption.
At The Hosting Hotel, our view is that most small business owners should never need to hear terms like DNS, nameservers, MX records, or TTL during normal hosting. Those details should be handled in the background. They tend to become visible only during a migration or when something unusual needs attention.
That is why we handle domain connection and DNS setup for members rather than expecting them to learn a system they may only touch once every few years.
If you are setting up a new website or want help moving an existing one, contact The Hosting Hotel and we can help you get everything connected properly.
Frequently Asked Questions
Do I need to transfer my domain to my hosting provider?
No. Your domain can remain registered with one company while your website is hosted somewhere else. You only need to configure DNS so the domain points to the correct hosting server.
Should I change nameservers or update the A record?
Change nameservers when you want the new provider to manage the entire DNS zone. Update individual DNS records when you want to keep your current DNS provider and change only where the website points.
Will changing nameservers break my email?
It can if the new DNS provider does not have the MX and other records your email service requires. Check and preserve existing email records before changing nameservers.
How long does it take for a domain to connect to hosting?
Individual DNS record changes are often visible within minutes or a few hours. Nameserver changes may take several hours and can sometimes take 24 to 48 hours to be reflected widely.
Can I connect a domain registered with one company to hosting from another?
Yes. That is a normal setup. The registrar, DNS provider, and hosting provider do not have to be the same company.
Why does my domain work without www but not with www?
The DNS record or hosting configuration for the www version may be missing. Check the CNAME or other record used for www, and confirm your hosting account recognizes both versions of the domain.