The short answer

Use the exact connection method your website platform provides. You will either replace the domain’s nameservers so the platform or DNS provider manages the whole DNS zone, or keep the current nameservers and add specific records such as A and CNAME records.

Do not mix instructions from two tutorials. First identify where DNS is currently managed, preserve the working records, and then follow one provider’s current instructions from beginning to end.

Choose between two connection methods

Method 1: Change nameservers

This delegates DNS management to a different provider. It can be convenient because that provider controls the full zone. It is also the riskier change when the domain already has business email, verification records, or other services.

Before changing nameservers, copy every active record into the new DNS zone. Missing MX or email-authentication records can make the website work while business email stops.

Method 2: Change only website records

Keep the existing nameservers and edit the records that direct website traffic. A provider may ask for:

• an A record for the root or apex domain, often shown as @.
• an AAAA record for an IPv6 destination.
• a CNAME record for www.
• a verification TXT or CNAME record.

Use the exact hostname, value, and proxy setting supplied by your provider. Do not substitute an IP address from an old tutorial.

Use this safe change sequence

1. Identify the registrar. This is where the domain is registered.
2. Identify the authoritative nameservers. They reveal which DNS provider is publishing the live records.
3. Export or photograph the existing zone. Include website, email, verification, and security records.
4. Copy the platform’s current instructions. Record the exact values and the date you retrieved them.
5. Decide whether you are changing nameservers or individual records. Do not do both unless the provider explicitly requires it.
6. Make the smallest necessary change. Preserve unrelated email and service records.
7. Add the domain inside the website host. The host must be prepared to recognize it.
8. Wait for DNS caches and provider verification. Do not repeatedly replace correct values because the first test is still old.
9. Test the root domain and www. Also test email if any DNS delegation changed.
10. Record the final working configuration. Include screenshots and the reason for the change.

Cloudflare’s DNS documentation distinguishes nameserver management, DNS records, DNSSEC, proxying, and troubleshooting. Even if you use another provider, its organization is a useful reminder that these are separate settings. See Cloudflare DNS documentation.

Understand the host field

DNS editors label the same field differently. You may see Name, Host, or Hostname.

• @ usually represents the bare domain, such as example.com.
• www represents www.example.com.
• _service or another prefixed value may be a verification or authentication record.

Do not type the full domain into a panel that automatically appends it unless the provider’s example shows that format. Otherwise you may accidentally create something like www.example.com.example.com.

Test more than the homepage

After the connection appears active, check:

• https://example.com.
• https://www.example.com.
• an internal page.
• a form submission.
• the secure certificate on both hostnames.
• incoming and outgoing business email.
• any scheduling, checkout, or member-area subdomain.

Test on a phone using mobile data as well as your regular internet connection. Different networks may hold different cached DNS answers during a change.

Know when to stop changing things

If an authoritative DNS lookup shows the new value but your own device shows the old one, the change may simply be cached. If the authoritative lookup itself is wrong, waiting will not repair the configuration.

When asking support for help, send:

• the domain and affected hostname.
• current nameservers.
• the record type, host, and value you entered.
• the provider instruction you followed.
• the time of the change.
• the exact error and where you saw it.
• what the authoritative lookup returns.

That evidence lets support diagnose the connection instead of telling you to wait another 48 hours by default.

Sources and further reading

• Cloudflare DNS documentation

A free next step

You don't have to build this alone

Bring your questions, share what you're working on, and meet other women building businesses from home. It is free to join.

Join Our Community Free

Related Questions

• How do domains, DNS, and web hosting fit together when I set up a website?
• Where should I buy my domain, and should the registrar be separate from my web host?
• How long do DNS changes usually take, and when does a delay signal a real problem?
• Why does my domain point to the wrong website or work only with www?

Related WAHMN resource

If you want to turn this website task into a service or build a stronger process for your own site, this system walks through the work in more depth. See Website & Landing Page Build System.