Who it is for
This is for a small business owner or office manager who just changed something about their domain: moved DNS to a new provider (for example to Cloudflare), switched website hosts, renamed the business domain, or had a web person “point the domain” somewhere new. You do not need to know how DNS works in depth. You need about 30 minutes, a phone on cellular data, and login access to wherever your DNS now lives. The goal is to catch the quiet failures early: a site that loads for you but not for customers, a broken padlock, or email that stopped arriving.
What you need
- Login to your DNS provider (the place where you edit records today, which may not be where you bought the domain).
- A screenshot or export of your old DNS records, if you have one. Many providers let you export a zone file; if not, screenshots are fine.
- A phone that can switch off WiFi and use cellular data.
- A second email account (a personal Gmail or Outlook works) to send test messages.
- Optional: access to Google Search Console if your site already uses it.
Before you change anything
If you have not cut over yet:
- Export or screenshot every DNS record at the old provider. Pay special attention to MX, TXT (SPF, DKIM, verification codes), and CNAME records. These are the ones that go missing.
- A day ahead, lower the TTL on the records you plan to change (5 minutes is common). TTL is how long the rest of the internet caches your old answer, so a short TTL makes the switch faster and makes a rollback faster too (Cloudflare’s TTL reference).
- Pick a quiet time to cut over, not 4 PM on your busiest day.
Steps
1. Confirm the internet sees your new records
- Open Google Admin Toolbox Dig and type your domain (example:
yourshop.com). - Check the A (or CNAME) record. It should match the new host’s address, not the old one.
- Repeat for
www.yourshop.com. The bare domain and thewwwversion are separate records and are often configured differently. - Check NS (name servers). If you moved DNS providers, these should show the new provider’s name servers. If they still show the old ones, the change at your domain registrar has not finished or was never made.
If the answers are still old, wait out the old TTL and check again. If they are still old after a few hours, the change was saved in the wrong place.
2. Load the site the way a customer would
- On your phone, turn WiFi off so you are on cellular data. This avoids your office router’s cached answer.
- Visit
https://yourshop.comandhttps://www.yourshop.com. Both should load the new site and land on the same address. - Visit
http://yourshop.com(no “s”). It should redirect to thehttps://version. - Click through the pages customers actually use: home, contact, services, booking or quote form.
- Do the same on a desktop browser in a private or incognito window.
3. Check HTTPS and the padlock
- In the browser, click the padlock or site-info icon next to the address. It should say the connection is secure.
- If you see a certificate warning, the new host may still be issuing the certificate. Most hosts do this automatically within minutes to an hour once DNS points at them. If it persists past that, the host cannot see the domain yet, usually because DNS still points somewhere else.
- Watch for “mixed content”: the page loads but images or forms are missing. That often means the site still links to the old address with
http://.
4. Make sure email still works
This is the most common casualty of a DNS move. Website and email are separate, and moving one can quietly break the other.
- In the Dig tool, look up MX for your domain. It should still point at your email provider (for example Microsoft 365 or Google Workspace), unless you intentionally changed email too.
- Look up TXT and confirm your SPF record (starts with
v=spf1) is still there. If you use DKIM, check those CNAME or TXT records too. Your email provider documents exactly which records it expects (Microsoft 365 DNS records). - Look up
_dmarc.yourshop.com(TXT). If you had a DMARC record before, it should still be there (Google Workspace DMARC setup). - From your personal email account, send a message to your business address. Then reply from the business address back to the personal one. Check that the reply did not land in spam.
5. Test your forms and anything that sends mail
- Submit your contact or quote form with a test message that clearly says “TEST.”
- Confirm it arrives where it should. Website forms often send through a separate service whose own DNS records (SPF or DKIM) need to be carried over.
- If you take bookings or payments through the site, run one test through the confirmation email.
6. Tell Google about the change (if you use Search Console)
- Open Search Console and confirm the property still shows as verified. A DNS move can drop the TXT verification record (verify your site ownership).
- If you changed to a new domain name, the old domain should redirect page-by-page to the new one, not just to the new home page. Ask your web person to confirm this before you let the old domain lapse.
- Resubmit your sitemap if your host or site structure changed.
7. Check the small stuff people forget
- Subdomains:
shop.,booking.,portal.,mail.or anything else that used to work. - Third-party verification records (Microsoft, Google, Facebook, payment processors) that live as TXT records.
- Your Google Business Profile and social profiles still link to the right address.
- Printed material and email signatures if the domain name itself changed.
Caution
- Do not delete the old DNS provider or hosting account the same day. Keep it for at least a week so you can compare records or roll back.
- Do not let an old domain expire after a rename. Someone else can register it and receive your customers’ email and traffic.
- “It works on my computer” is not a test. Your office may cache the old answer for hours. Always check from cellular data or an outside tool.
- If you use a proxy or CDN in front of your site (for example Cloudflare’s orange-cloud proxy), the A record will show the provider’s addresses, not your host’s. That is expected.
- Write down what you changed and when. If something breaks next month, that note saves hours.