DNS and SSL for new website owners

A domain name, DNS service and web host can be bought from the same company, but they remain separate layers. DNS tells the internet where a hostname goes; hosting answers the request; TLS provides the HTTPS certificate.

Nameservers decide where DNS is managed

If you change nameservers, future DNS records are normally managed at the new DNS provider rather than the previous one.

Propagation is mostly caching

DNS changes can appear at different times because recursive resolvers cache earlier answers. A new domain may therefore work on one network before another.

SSL usually follows correct DNS

Automated certificate systems generally need the hostname to point at the expected hosting service before issuance and validation can finish reliably.

Know the difference between delegation and records

Nameserver settings delegate responsibility for the DNS zone. Records inside that zone—such as A, AAAA, CNAME, MX and TXT records—then describe individual services. Changing nameservers is therefore a larger operation than changing one A record.

Root domain and www can be separate

example.com and www.example.com are different hostnames. A site can work on one and fail on the other if their DNS or hosting configuration differs. Choose a preferred hostname, make both resolve intentionally and redirect the secondary version consistently.

TXT records have many jobs

TXT records are used for several unrelated purposes, including ownership verification and email authentication. It is normal for a root domain to contain multiple TXT records. Do not delete an SPF or verification record simply because you need to add another TXT value.

Email DNS is separate from website DNS

A website can work perfectly while email is broken. MX, SPF, DKIM and DMARC records deserve their own review when a domain sends or receives mail. Moving nameservers without recreating existing mail records is a common source of accidental outages.

A safe migration sequence

1. Record the current DNS zone.
2. Prepare the destination hosting and certificate configuration.
3. Create required DNS records at the new DNS provider before changing delegation when possible.
4. Change nameservers or records.
5. Verify the root domain, www, HTTPS, email and third-party verification tokens.
6. Only then remove obsolete hosting.