DNS

Connect your website without accidentally disconnecting your email

Understand records and nameservers, preserve the services you already use, and verify the public result after a DNS change.

By NeoWeb editorial2 min read
A silver envelope linked by a blue cable to an architectural doorway.

Map the services first

A domain can carry a website, business email, verification records and product subdomains at the same time. Before changing anything, list the services that rely on it. Save the current DNS records and identify where authoritative DNS is managed.

Moving the website does not necessarily require moving every other service. A narrow record change is often easier to verify than replacing the entire DNS setup.

Distinguish records from nameservers

Records describe where particular services should resolve. Nameservers identify the system that answers DNS queries for the domain. Changing nameservers can make the old record set ineffective unless those records also exist at the new provider.

Keep email delivery records, sender authentication records and ownership challenges in your review. Do not delete a TXT record merely because its purpose is not obvious; identify the service that created it.

Apply the instructions for the right hostname

The root domain, a www hostname and an application subdomain are different targets. Follow the website provider’s exact instructions for each. Avoid putting one product’s address over another product’s existing record.

  • Confirm the hostname you are connecting.
  • Review conflicting records.
  • Make the smallest required change.
  • Keep a record of the previous value.

Verify more than the settings screen

A saved setting is not proof that public DNS has changed everywhere. Check resolution, open the site over HTTPS and verify the certificate. Test business email again. Cached DNS responses can take time to reflect the new values.

NeoDomains keeps domain management and website connection steps together. Successful connection should be based on DNS and HTTPS evidence, not on opening a builder link.

If the result is wrong, compare the new configuration with your saved record set and use the provider’s support channel. Avoid repeatedly replacing nameservers while the previous change is still propagating.

Sources & further reading

Primary sources used for the specific guidance in this article. Product instructions and the actual offer take precedence for your transaction.

Your next step

Find an address that feels like you. Compare registration and renewal costs, manage your domain portfolio, and keep the details of ownership within reach.

Explore NeoDomains