DNS

The browser could not turn your domain into an IP address. Check the domain status in RDAP, then nameservers, records, glue and DNSSEC, then your own DNS cache.

Changed your URLs or domain? Build a complete old-to-new map, pick the right status code, put the rules in the right layer and test every line before and after launch.

Moved a WordPress site and it keeps sending you to the old domain or staging address? Find which layer is redirecting, then fix the database URLs safely, constants, DNS and CDN origin.

Move WordPress without a migration plugin: dump the database, copy the files, import, run a safe search-replace, test through your hosts file, then switch DNS.

Most broken Cloudflare moves come from a record the import scan missed, a proxied mail hostname or DNSSEC left on. Audit, compare and switch in the right order.

Usually the change was made at a DNS host your domain does not use, or a cache is holding the old answer. Ask the authoritative servers first, then work outward.

A subdomain needs three things: a DNS record, a server that knows the name, and a certificate that covers it. Test each one separately and the broken link shows itself.

A registrar transfer moves the registration, not your website or mail. Downtime comes from DNS hosted at the old registrar. Secure the zone first, then transfer.

Web records point at the web host and mail records point at the mail provider. Mail breaks when a new host replaces the zone, or its server still thinks it handles your mail.

Your site no longer shows up on Google, even for its own name. Find the cause fast: noindex, robots.txt, a manual action, a hack, an outage or a canonical pointing elsewhere.

Set up Google Workspace email on your own domain the right way: verification, the MX record, SPF, DKIM in the Admin console and DMARC, without breaking website mail.

Connect your domain to Microsoft 365 the right way: verification, MX, autodiscover, SPF, DKIM in the Defender portal and DMARC, plus what to do about website SMTP mail.