Explainer5 min readUpdated 7 Sept 2026

What happens after you save the DNS change

Know what AlphaBlue checks, why an update may not appear immediately and when setup is truly complete.

Saving the nameserver or CNAME change finishes your part of the guided task. It does not mean you should keep changing settings until the website appears.

Send the requested screenshot to AlphaBlue and wait for verification. Repeated edits can restart activation, create a conflict or make the original problem harder to identify.

DNS updates are not always visible everywhere at once

DNS information is cached by providers, networks and devices. A correct change may appear on one connection before another. Provider help pages commonly warn that nameserver changes can take up to 24 or 48 hours, although many changes appear sooner.

This does not mean every problem is propagation. AlphaBlue checks the actual DNS answers and Cloudflare status rather than asking you to wait blindly.

What AlphaBlue verifies

For AlphaBlue-managed DNS

  • the registrar publishes the exact assigned Cloudflare nameservers;
  • no old nameserver remains in the delegation;
  • the Cloudflare zone status is Active;
  • important copied records answer from Cloudflare;
  • the site is attached to the intended Pages project or Worker;
  • DNSSEC is either safely disabled for migration or correctly re-enabled afterward.

For a customer-managed Pages CNAME

  • the public CNAME has the expected hostname and target;
  • the hostname was already registered in the Pages project;
  • Pages reports the Custom Domain as active;
  • no conflicting A, AAAA or CNAME remains at the same hostname.

For both paths

  • HTTPS loads without a certificate warning;
  • the agreed root, www and selected subdomain behaviour is correct;
  • redirects end at the intended primary address;
  • the page belongs to the correct customer and production release;
  • agreed contact actions and forms work;
  • domain email can still send and receive when the customer uses it.

What we may ask you to test

AlphaBlue may ask you to:

  1. open the website on Wi-Fi and mobile data;
  2. submit an agreed test form;
  3. send an email from the domain mailbox to an external address;
  4. reply from the external address back to the domain mailbox;
  5. confirm that no browser security warning appears.

Email testing requires the mailbox owner because DNS checks alone cannot prove that a real message reaches the correct inbox and can be sent successfully.

When setup is complete

The setup is complete only when AlphaBlue confirms the agreed website addresses, HTTPS and relevant service checks. Until then:

  • do not add another record for the same hostname;
  • do not switch nameservers back and forth;
  • do not reset DNS;
  • keep screenshots and provider messages;
  • report any website or email outage immediately.

Official references

Technical requirements last verified: 7 September 2026.