How to Connect a Domain to a Website or Web Hosting: Nameservers, DNS Records, Email, SSL, and Verification

To connect a domain to a website, you need to make the domain’s DNS point to the service that hosts the website.

There are two main ways to do this:

1. Change the domain's nameservers to the nameservers provided by your hosting, DNS, or website platform; or
2. Keep the current nameservers and add or update DNS records such as A, AAAA, or CNAME records at the DNS provider that is already authoritative for the domain.

The correct method depends on where you want DNS to be managed.

If your domain is registered at NiceNIC, you can either update the domain's nameservers or, when using NiceNIC's default nameservers, manage the DNS records directly at NiceNIC.

Before changing anything, identify your active nameservers, back up existing DNS records, and preserve email records such as MX, SPF, DKIM, and DMARC. Changing nameservers without recreating the full DNS zone can make the website work while breaking email, or vice versa.

For the underlying distinction between registrar, DNS, and hosting, see Domain Registrar vs Web Hosting.

Quick Answer: How Do You Connect a Domain to Hosting?

The most important rule is:

First decide who will host DNS. Then make the website records there.

What Does "Connect a Domain to a Website" Actually Mean?

A domain registration and a website are separate things.

For example:

example.com

may be registered at one company while the website itself runs at another hosting provider.

DNS connects them.

A simplified path looks like this:

Domain registration → Nameservers → DNS records → Hosting server / website platform → Website

If you already bought the domain but the website is not live yet, the missing step is usually:

telling DNS where the website is located.

Domain, DNS, and Hosting Are Three Different Layers

These can all be with the same company.

They can also be with three different companies.

For example:

Registrar: NiceNIC DNS: Cloudflare Hosting: another hosting provider

That is a normal configuration.

NiceNIC also documents that you can use Cloudflare DNS without transferring the domain away from NiceNIC.

Before You Start: Collect These Details

Do not start changing DNS until you have the information required by the hosting or website provider.

Prepare:

• your domain name;
• registrar login;
• current nameservers;
• current DNS provider;
• hosting account;
• the hosting provider's setup instructions;
• destination IP address if provided;
• required CNAME target if provided;
• current DNS records;
• email provider details;
• DNSSEC status;
• current SSL/HTTPS status.

If the domain already runs email or another live service, save the DNS zone before making changes.

The Two Main Ways to Connect a Domain

Method 1: Change the Nameservers

Use this method when your hosting provider, website builder, or DNS provider wants to manage the entire DNS zone.

For example, your provider may give you:

ns1.examplehost.com

ns2.examplehost.com

You then update the domain’s nameservers at the registrar.

After the change, DNS records are managed at the new nameserver provider.

Method 2: Keep the Nameservers and Change DNS Records

Use this method when you want to keep the current DNS provider.

For example:

Registrar: NiceNIC Nameservers: NiceNIC DNS: NiceNIC Hosting: External Host

The host may tell you:

Point your domain to 203.0.113.20

You keep the existing nameservers and update the A record.

This method can be safer when:

• business email is already working;
• many DNS records already exist;
• you do not want to move DNS;
• only the website destination needs to change.

Nameservers vs DNS Records: What Is the Difference?

This distinction is critical.

Nameservers

Nameservers tell the internet:

Where is this domain's authoritative DNS zone hosted?

DNS records

DNS records inside that zone tell services:

Where should the website, email, or other services go?

For example:

Nameservers

ns1.dnsprovider.com

ns2.dnsprovider.com

identify the DNS provider.

A Record

example.com → 203.0.113.20

identifies the web server.

MX Record

example.com → mail.exampleprovider.com

identifies the email server.

Changing nameservers changes where DNS records are managed.

Changing an A record changes one specific destination inside DNS.

Which Method Should You Choose?

Use this decision table.

Do not switch nameservers merely because a hosting provider gives you an IP address.

An IP address normally belongs in an A or AAAA record.

Method 1: Connect the Domain by Changing Nameservers

Use this method when the new provider wants to manage DNS.

Step 1: Get the Exact Nameservers

Your hosting or DNS provider should supply names such as:

ns1.examplehost.com

ns2.examplehost.com

Copy them exactly.

Do not invent nameservers.

Step 2: Back Up Existing DNS

Before changing nameservers, save:

• A;
• AAAA;
• CNAME;
• MX;
• TXT;
• SPF-related records;
• DKIM;
• DMARC;
• CAA;
• SRV;
• verification records;
• important subdomains.

This matters because:

Changing nameservers does not automatically copy DNS records from the old DNS provider to the new one.

If email already works, this step is especially important.

Step 3: Recreate the Required Records at the New DNS Provider

Do this before changing the nameservers when possible.

At the new provider, create:

• website records;
• email records;
• service-verification records;
• security records;
• subdomain records.

Do not wait until after the nameserver change to discover that the new DNS zone is empty.

Step 4: Change Nameservers at NiceNIC

For a NiceNIC-registered domain:

1. sign in to your NiceNIC account;
2. open the domain under My Products;
3. open the domain-management page;
4. choose Domain Services;
5. enter the new nameservers;
6. save the change.

Use the current NiceNIC nameserver update guide for the latest interface steps.

What If the Nameserver Update Is Rejected?

Some registries validate nameservers before accepting them.

NiceNIC’s current nameserver guidance explains that updates can fail when the nameservers:

• are not configured correctly;
• do not respond;
• are not authoritative;
• fail registry technical validation.

If the update fails:

1. confirm the spelling;
2. ask the DNS/hosting provider to confirm the nameservers are live;
3. confirm they are authoritative for your domain;
4. fix the DNS-provider setup;
5. retry the nameserver update.

Repeatedly submitting the same invalid nameservers will not solve the problem.

Method 2: Keep NiceNIC Nameservers and Point DNS to the Host

This method keeps DNS at NiceNIC.

NiceNIC's current DNS Services guide explains the key rule:

NiceNIC DNS records are used when the domain delegates to NiceNIC nameservers.

If your domain uses external nameservers, edit DNS at that external provider instead.

Step 1: Get the Required Records From the Host

Your hosting provider may give you:

• an IPv4 address;
• an IPv6 address;
• a CNAME destination;
• TXT verification record;
• custom subdomain instructions.

Do not guess the values.

Use the exact information supplied by the service you are connecting.

Step 2: Open NiceNIC DNS Management

When the domain uses NiceNIC nameservers:

1. sign in to NiceNIC;
2. open the domain from My Products;
3. open the domain-management page;
4. choose DNS Records;
5. add or edit the required records;
6. save the changes.

See How to Manage DNS Records at NiceNIC.

Step 3: Configure the Root Domain

The root domain is:

example.com

It is also sometimes called:

• apex;
• bare domain;
• root domain.

Your hosting provider may instruct you to create an A record:

Different DNS interfaces represent the root differently.

NiceNIC’s current DNS interface may use a blank or designated root host depending on the record type.

Follow the actual interface and provider instructions rather than typing the full domain into a field that expects only the host label.

Step 4: Configure www

These are two separate DNS names:

example.com

www.example.com

A common setup is:

But your hosting provider may require a different www target.

Use its official value.

Do not assume configuring the root domain automatically configures www.

A Record vs CNAME: Which Should You Use?

A Record

Use an A record when the provider gives you an IPv4 address.

Example:

example.com → 203.0.113.20

AAAA Record

Use an AAAA record when the provider gives you an IPv6 address.

CNAME Record

Use a CNAME when the provider gives you another hostname.

Example:

www.example.com → sites.exampleplatform.com

Do not put an IP address into a CNAME field.

What About Website Builders?

Website builders often provide:

• CNAME records;
• A records;
• TXT verification records.

For example, a platform may ask you to add:

www → connect.platform.example

and:

TXT → platform-verification-code

You generally do not need to transfer the domain to the website builder.

Keep the registration at NiceNIC and enter the records at the active DNS provider.

How to Connect a Domain to a VPS or Cloud Server

A VPS or cloud server typically gives you an IP address.

A common setup is:

But DNS is only half the setup.

The server must also be configured to accept the domain.

That may require:

• web-server virtual host;
• Nginx/Apache configuration;
• application hostname;
• SSL certificate;
• firewall access;
• port 80/443 availability.

If DNS points correctly but the server is not configured for the hostname, the domain may show:

• default server page;
• another website;
• 404;
• 403;
• connection error.

How to Connect a Domain to Shopify, Wix, Squarespace, or Another Website Platform

The general principle is the same.

The platform will normally provide:

• nameservers; or
• A/CNAME/TXT records.

Do not follow a random tutorial using values from another platform.

Use the exact custom-domain instructions from your platform.

Then enter those values at:

the provider that is authoritative for your DNS.

The registrar can remain NiceNIC.

How to Connect a Domain While Using Cloudflare

You can keep:

Registrar: NiceNIC DNS: Cloudflare Website: any compatible hosting provider

In this configuration:

1. NiceNIC holds the domain registration;
2. the domain uses Cloudflare nameservers;
3. DNS records are managed in Cloudflare;
4. website records point from Cloudflare to the host.

NiceNIC documents this setup in Can You Use Cloudflare DNS Without Transferring Your Domain?.

Do not create the same records at NiceNIC expecting them to affect the live site if Cloudflare nameservers are authoritative.

Protect Email Before Changing Nameservers

This is one of the most important steps in the entire process.

A website connection often focuses only on:

• A record;
• CNAME.

But business email may depend on:

• MX;
• SPF;
• DKIM;
• DMARC;
• verification TXT records;
• autodiscover records.

If you switch nameservers and forget these records:

the website may work while email stops.

Before changing nameservers, copy the complete mail-related DNS setup.

Example: Website at One Provider, Email at Another

A normal DNS zone might look like:

When connecting a new website, change only the records required for the website unless you intentionally want to change email too.

Do not delete unrelated DNS records.

Does Changing an A Record Affect Email?

Usually not directly.

An A record used for the website and MX records used for email are different DNS records.

However, email can still be affected if:

• the mail server hostname depends on the changed A record;
• you delete supporting records;
• you change nameservers and fail to recreate the mail records.

So:

Changing one website A record is not the same as replacing the entire DNS zone.

Check DNSSEC Before Changing Nameservers

If DNSSEC is enabled, nameserver changes need extra care.

NiceNIC's current DNSSEC setup and troubleshooting guide explains that DNSSEC records are usually generated by the DNS provider, while NiceNIC can submit the relevant DS record to the registry for supported TLDs.

A common failure sequence is:

1. domain uses DNS Provider A;
2. DNSSEC is active;
3. DS record points to Provider A's keys;
4. nameservers change to Provider B;
5. old DS record remains;
6. Provider B uses different DNSKEY data;
7. DNS validation fails.

Users may then see:

SERVFAIL

even though the normal A record appears correct.

Before changing nameservers:

• check whether DNSSEC is enabled;
• confirm whether DS records must be removed or replaced;
• enable signing correctly at the new provider;
• verify the chain after the change.

DNSSEC and SSL Are Different

Do not confuse them.

DNSSEC

Helps verify DNS responses.

SSL/TLS

Protects the connection between the browser and the website.

A domain can have:

• correct DNS;
• valid DNSSEC;
• broken SSL.

Or:

• valid SSL certificate;
• broken DNS.

Troubleshoot them separately.

When Should You Configure SSL?

Usually after the domain points to the correct hosting service.

Many hosting platforms automatically issue a certificate after DNS verification.

Others require you to:

• enable SSL manually;
• install a certificate;
• verify the domain;
• configure HTTPS.

Test:

http://example.com

and:

https://example.com

Also test:

https://www.example.com

if you use www.

The certificate should cover every hostname users are expected to visit.

Why Does HTTP Work but HTTPS Fail?

Possible causes include:

• certificate not issued;
• certificate expired;
• certificate does not include the hostname;
• HTTPS not enabled at the host;
• proxy/CDN SSL mismatch;
• redirect configuration.

If DNS resolves correctly but HTTPS fails, the registrar may not be the problem.

Check the hosting, SSL, or CDN layer.

What Is DNS Propagation?

After changing DNS, some users may temporarily receive older cached DNS answers.

DNS changes are not literally copied to every computer at once.

Recursive resolvers cache DNS information according to TTL and other caching behavior.

The useful distinction is:

Authoritative DNS

What the domain’s DNS provider says right now.

Cached DNS

What another resolver may still remember from an earlier query.

This is why one user may see the new website while another still sees the old one.

How Long Does DNS Propagation Take?

There is no universal fixed time.

It can depend on:

• previous TTL;
• resolver cache;
• delegation cache;
• negative caching;
• ISP resolver;
• local DNS cache.

Do not simply wait 24-48 hours without checking the configuration.

NiceNIC’s current DNS guidance recommends:

1. confirm the authoritative provider;
2. verify the authoritative record is correct;
3. only then allow cached answers to expire.

See Why Your DNS Changes Are Not Working and How to Fix It.

Waiting Does Not Fix a Wrong DNS Record

This deserves its own rule:

Propagation cannot correct a misconfiguration.

If the authoritative DNS says:

example.com → wrong IP

waiting longer will not make it become the correct IP.

Fix the authoritative record first.

Then consider caching.

How Do You Verify the Domain Is Connected Correctly?

Do not stop when the DNS panel says:

Saved

Test the actual service.

Check 1: Root domain

Open:

example.com

Check 2: www

Open:

www.example.com

Check 3: HTTP

Test:

http://example.com

Check 4: HTTPS

Test:

https://example.com

Check 5: Another network

Try:

• Wi-Fi;
• mobile data;
• another resolver.

Check 6: Email

If the domain uses business email:

• send a test message in;
• send one out.

Check 7: Important subdomains

Test:

• shop;
• app;
• login;
• API;
• mail;
• any production subdomain.

Do not consider the setup complete until all required services work.

Website Connection Verification Checklist

Root Works but www Does Not

Check the www record.

Common setup:

www → CNAME → example.com

But some website platforms require their own specific CNAME target.

Use the host’s instructions.

Also ensure the SSL certificate covers:

www.example.com

www Works but the Root Domain Does Not

Check:

• root A record;
• root AAAA record;
• apex-specific record required by the provider;
• whether your DNS provider supports the required apex configuration.

Do not add a conventional CNAME at the zone apex unless your DNS provider/platform specifically supports an appropriate equivalent mechanism.

Why Does the Old Website Still Appear?

Possible causes:

• old A record still authoritative;
• you edited DNS at the wrong provider;
• local/resolver cache;
• CDN cache;
• browser cache;
• old IPv6 AAAA record;
• hosting redirect.

Check authoritative DNS first.

Why Does the Wrong Website Appear?

Possible causes:

• DNS points to wrong server;
• shared server does not recognize the domain;
• virtual host is not configured;
• CDN route is wrong.

If the correct IP is returned but another website appears, check the hosting configuration.

Why Does the Website Show "Server Not Found"?

Check:

1. domain status;
2. nameservers;
3. authoritative DNS;
4. required A/CNAME records;
5. DNSSEC if SERVFAIL appears.

If the domain is active but DNS does not resolve, use the NiceNIC troubleshooting guide Why Is My Domain Active but My Website Not Working?.

Why Does the Hosting Provider Say the Domain Is Not Connected?

Many hosting platforms verify DNS automatically.

Possible reasons include:

• incorrect A record;
• missing CNAME;
• wrong TXT verification;
• DNS changed at wrong provider;
• cached old result;
• conflicting AAAA record;
• platform has not rechecked yet.

Compare the DNS values character by character with the provider’s instructions.

Common DNS Input Mistakes

NiceNIC’s current DNS troubleshooting guidance identifies common errors such as:

• using the full domain where only @ or www is expected;
• putting an IP address into a CNAME;
• leaving an old AAAA record;
• creating conflicting records;
• editing DNS at the wrong provider.

Do not “experiment” with DNS until something works.

Follow the destination service’s exact instructions.

Can You Connect One Domain to Multiple Services?

Yes.

DNS can direct different hostnames or services independently.

For example:

example.com → website

shop.example.com → ecommerce platform

app.example.com → SaaS application

MX → business email

TXT → verification / SPF / DKIM / DMARC

One domain can support many services at the same time.

This is another reason not to delete unrelated DNS records when connecting a new website.

Can You Point Multiple Domains to One Website?

Yes.

For example:

brand.com

brand.net

brand.co

can all be configured to reach one website.

The recommended setup often involves:

• one primary domain;
• redirects from alternate domains;
• consistent HTTPS;
• correct canonical URLs at the website level.

Do not serve identical sites from many domains without a clear canonical/redirect strategy if organic search matters.

Do You Need to Transfer the Domain to the Hosting Company?

No.

Connecting a domain and transferring a domain are different operations.

To use a hosting provider, you usually only need to:

• change nameservers; or
• update DNS records.

A registrar transfer is only required if you actually want to change which registrar manages:

• renewal;
• transfer;
• registrar lock;
• domain-registration controls.

If you want to move an existing registration instead, use the NiceNIC Domain Transfer service.

Do You Need to Change Hosting When You Transfer a Domain?

No.

A registrar transfer does not automatically move:

• website files;
• database;
• hosting account;
• email.

If nameservers remain unchanged, existing website services can normally continue using the same DNS and hosting setup.

Can You Connect a Domain Before the Website Is Finished?

Yes.

You can point the domain to:

• a staging site;
• coming-soon page;
• website builder;
• maintenance page.

Or you can leave the domain registered without connecting it until the website is ready.

There is no requirement that registration and website launch happen simultaneously.

When Should You Change Nameservers Instead of DNS Records?

Change nameservers when you intentionally want another provider to become responsible for the whole authoritative DNS zone.

Typical reasons:

• adopting Cloudflare;
• letting the hosting company manage all DNS;
• migrating to a dedicated DNS provider;
• replacing an old registrar DNS service.

If you only need to change where the website points, a record change may be simpler and safer.

When Should You Change Only DNS Records?

Edit DNS records when:

• website server IP changes;
• adding a website builder;
• adding a subdomain;
• connecting SaaS;
• configuring email;
• adding verification records.

In these situations, there may be no reason to change nameservers.

How to Move Hosting Without Breaking Email

Use this safer process:

1. inventory existing DNS;
2. identify mail records;
3. build the new website first;
4. verify the new server;
5. update only website-related DNS;
6. leave mail records unchanged;
7. test email;
8. keep old hosting available until verification completes.

If you change nameservers, recreate all email records at the new DNS provider before the switch.

How to Connect a Domain Without Downtime

For an existing live site:

Step 1

Prepare the new hosting first.

Step 2

Add the domain at the new host.

Step 3

Verify the new site using a temporary URL or hosts-file method where appropriate.

Step 4

Back up DNS.

Step 5

Confirm email records.

Step 6

Change only the required DNS destination.

Step 7

Keep the old server active during the transition.

Step 8

Test from multiple networks.

Step 9

Retire the old service only after the new setup is verified.

This reduces the risk of changing infrastructure before the destination is ready.

Who Should You Contact When the Connection Fails?

The provider that sold the domain is not automatically responsible for every website problem.

Symptom → Likely Cause → Fix

A 10-Minute Domain-to-Website Setup

If you need the fastest safe workflow:

Minute 1

Open your hosting provider’s custom-domain instructions.

Minute 2

Check your domain’s current nameservers.

Minute 3

Decide whether to:

• change nameservers; or
• keep DNS and add records.

Minute 4

Back up existing DNS.

Minute 5

Preserve email records.

Minute 6

Add the website records or prepare the new DNS zone.

Minute 7

Make the nameserver/DNS change.

Minute 8

Check authoritative DNS.

Minute 9

Test root, www, HTTP, and HTTPS.

Minute 10

Test email and important subdomains.

Common Mistakes

"I bought hosting, so the domain will automatically connect."

Not necessarily.

The registrar and host may be separate systems.

"I changed nameservers, so my old DNS records will move automatically."

No.

Recreate required records at the new provider.

"I changed the A record but nothing happened, so I should wait 48 hours."

First verify that you edited DNS at the authoritative provider and that the authoritative record is correct.

"I only need the website records."

Not if the domain also uses email or other services.

"I should change both nameservers and A records at the registrar."

Not necessarily.

If you switch to external nameservers, DNS is normally managed there.

"I must transfer the domain to use another host."

No.

Registrar and hosting are separate.

"DNSSEC and SSL are the same."

No.

They protect different layers.

Frequently Asked Questions

How do I connect a domain to a website?

Either change the domain’s nameservers to the DNS/hosting provider or keep the existing nameservers and update the required A, AAAA, CNAME, or other DNS records.

How do I connect a NiceNIC domain to external hosting?

Use the nameservers supplied by the hosting provider or keep NiceNIC nameservers and add the DNS records supplied by the host.

Should I change nameservers or A records?

Change nameservers if another provider should manage the entire DNS zone. Change A/CNAME records if you want to keep DNS at the current provider.

Where do I manage DNS if my domain is registered at NiceNIC?

If the domain uses NiceNIC nameservers, use NiceNIC DNS management. If it uses external nameservers, manage DNS at the external DNS provider.

Can I use Cloudflare without transferring my domain?

Yes. Keep the domain at NiceNIC and use Cloudflare nameservers/DNS.

What is an A record?

An A record maps a hostname to an IPv4 address.

What is a CNAME?

A CNAME aliases one hostname to another hostname.

Do I need both root and www DNS records?

Usually yes if you want both hostnames to work.

How long do DNS changes take?

There is no universal fixed time. The authoritative update can be immediate while cached answers remain until their TTL expires.

Should I wait 24-48 hours after every DNS change?

Not blindly. First verify that the authoritative DNS is correct.

Will changing nameservers break email?

It can if the new DNS zone does not contain the required MX, SPF, DKIM, DMARC, and other mail records.

Does changing hosting require a domain transfer?

No.

Does changing the registrar require moving hosting?

No.

Why does HTTP work but HTTPS not work?

The DNS may be correct while SSL or hosting HTTPS configuration is incomplete.

Why does my old site still show?

Check authoritative DNS, old AAAA records, resolver cache, CDN cache, and browser cache.

What if my domain is active but the website still does not load?

Use NiceNIC's website and DNS troubleshooting guide.

Final Domain-to-Website Checklist

Before considering the setup complete, confirm:

• Domain is registered and active.
• Correct nameservers are delegated.
• You know which provider is authoritative for DNS.
• DNS backup exists.
• Root domain points correctly.
• www points correctly.
• No conflicting old A/AAAA/CNAME records remain.
• MX records are intact.
• SPF is intact.
• DKIM is intact.
• DMARC is intact.
• DNSSEC is valid if enabled.
• Hosting recognizes the domain.
• Website files/application are ready.
• HTTP works.
• HTTPS works.
• SSL covers all required hostnames.
• Email has been tested.
• Important subdomains have been tested.
• Another network or resolver has been tested.
• Old hosting is not cancelled until the new setup is verified.

The safest way to think about connecting a domain is:

Choose who manages DNS → configure the destination correctly → preserve existing services → verify the real result.

Do not change several layers at once unless you understand exactly why each change is required.

Connect and Manage Your NiceNIC Domain

• Update your domain's nameservers
• Manage DNS records at NiceNIC
• Review how DNS works at NiceNIC
• Use Cloudflare DNS without transferring your domain
• Troubleshoot DNS changes that are not working
• Set up and troubleshoot DNSSEC
• Understand the difference between a registrar and hosting
• Troubleshoot an active domain whose website is not working
• Search and register a domain
• Transfer a domain to NiceNIC

Primary Sources and Further Reading

• Cloudflare Learning Center — What Is DNS?
• Cloudflare Docs — Nameservers
• Cloudflare Learning Center — DNS TTL
• NiceNIC — DNS Services
• NiceNIC — How to Manage DNS Records
• NiceNIC — How to Update Domains' Nameservers
• NiceNIC — Why Your DNS Changes Are Not Working
• NiceNIC — Can You Use Cloudflare DNS Without Transferring Your Domain?
• NiceNIC — DNSSEC Setup and Troubleshooting