Domains and DNS are the part of a project where a mistake costs the most: the site stops opening and email quietly stops arriving. There are not many actions involved, and all of them are predictable once it is clear what each setting is responsible for.
The first decision: whose name the domain is in
The domain should be registered to the company or its owner, not to a contractor, a designer or an employee who once helped with the launch. It is an asset: when the supplier changes, the site and the email leave with the domain.
Check two things: which contact details are on the registrar account, and which mailbox receives renewal notices. Email on the same domain is a poor choice: if the domain lapses, the notice that it has lapsed will never reach you.
Three ways to point a domain at a site
- Change the NS servers to the hosting name servers - all domain records are then managed in the hosting panel; the simplest option for a single project
- Keep NS at the registrar and set an A record to the server IP - suitable when email and the site live in different places
- Use an external DNS provider - needed for fast TTL changes, protection or complex routing rules
How to move a site without downtime
The order is simple and well tested. A day before the move, lower the TTL on the relevant records so changes propagate quickly. Deploy the site on the new hosting and check it through a temporary address or the hosts file while the domain still points at the old server.
Once verified, change the A record or the NS and wait for propagation. Do not switch the old server off immediately: while DNS caches refresh, some visitors still arrive there. A day of parallel operation is usually enough.
Check the MX records separately. When NS servers change, mail records are often lost because the new zone is created from scratch - this is the most common reason corporate email suddenly disappears.
What to verify after switching
- The site opens with and without www, and redirects to the chosen primary version
- HTTPS works on the new server, with a valid certificate
- MX records are in place, and a test message arrives and sends
- SPF and DMARC text records moved across with the rest
- Domain verification records for external services were not removed
- Search Console shows no spike in availability errors
Frequently asked questions
How long should one wait after a DNS change?
It depends on the record TTL: usually from minutes to a day. The process cannot be accelerated retroactively - the TTL has to be lowered beforehand. Verify the result with an external DNS lookup rather than in your own browser, where caching may still apply.
Can a domain be transferred to another registrar without downtime?
Yes. Transferring registration and changing DNS are separate operations. If the NS servers stay the same during the transfer, the site and email keep working. Before transferring, the transfer lock has to be removed and an authorisation code obtained from the current registrar.
Why does the site open for some people and not others after a move?
Until the TTL of the old records expires, some providers keep returning the previous address. That is normal within a day. If the discrepancy lasts longer, check whether records remain in two places at once: in the registrar zone and in the hosting panel.
Need help with a domain and DNS?
Send the domain and describe the task: connection, migration or mail setup. We will review the current records and propose the steps.
Discuss your project ↗