A name is not a website subscription

Registering a domain gives you control over a name for a registration period. It does not necessarily include a website builder, email hosting, or a server. Those may be separate services even when a provider sells them together.

Map your own setup in plain language: where the domain is registered, which service manages DNS, and where the website files are hosted. Keep account recovery information privately, outside any public repository. This small inventory is useful when a provider changes or a renewal arrives.

DNS records serve different purposes

DNS helps clients discover information associated with names. An A record supplies an IPv4 address; a CNAME associates a name with another hostname. MX records route email, while TXT records can carry verification and email-policy information. Changing a website does not justify deleting unrelated records.

Before a migration, export the existing configuration and identify the exact records involved. If a hosting provider offers a custom-domain workflow, follow its documented process. A guessed record can lead to a reachable server that still cannot serve the intended site correctly.

Hosting delivers the actual response

The hosting service returns the files or application response a browser requests. A static host can serve pages generated in advance; a dynamic service may construct a response at request time. Both still need correct hostname and certificate configuration.

Test a new host using its temporary address before moving a production domain. Check inner pages, resources, HTTPS, and an unknown path. Prepare a rollback for the website records alone. A careful migration changes the smallest necessary part of a working system.

Further reading

Original sources and related references. These links lead to independent websites; inclusion does not imply a partnership or endorsement.

Browse the complete resource shelf →