Articles tagged with #DNS
The orange/grey cloud in Cloudflare DNS decides whether traffic hits the edge or your origin. The wrong state breaks SSL issuance, WebSockets, or origin masking. Here's how to pick the right one.
You turned on DNSSEC and validating resolvers now return SERVFAIL. Read the EDE code, regenerate the DS from the live DNSKEY, replace it at the registrar, or pull the DS to roll back. Verified June 2026.
IPv4 users reach the site fine but IPv6 users get timeouts. Either AAAA is absent, points to a dead address, or your firewall blocks v6. Fix dual-stack.
Delegated a subdomain to nameservers inside itself and resolution fails? The parent zone needs glue A/AAAA. Here is the dig diagnosis and the exact registrar fix.
Run en.yoursite.com and zh.yoursite.com on separate hosting regions to cut TTFB for each audience — without splitting SEO or breaking shared assets. Verified June 2026.
Same domain binds fine on Vercel but Firebase Hosting stays Pending or never gets SSL. The exact DNS records Firebase needs, what to remove, and how to confirm the fix.
You changed hosts but DNS still resolves to the old one. Run dig NS to find where your authoritative records actually live, then fix them at the right provider.
Google indexed all four versions of your site, splitting link equity four ways. The platform-level 301 + canonical plan that consolidates them into one.
Your site answers on both http and https, so Google indexes two copies and Chrome flags http as Not Secure. Add a 301 redirect plus an HSTS header to fix it.
Beginners confuse name servers (NS) and individual DNS records (A, CNAME). Changing one without understanding the other causes hours of debugging.
Google shows your-app.vercel.app or your-site.web.app in search instead of your custom domain. Why it happens and the exact redirect + canonical fix.
Moved old.com to new.com and now Search Console shows hundreds of 404s. How to build a complete redirect map, deploy it on the old domain, and verify every URL returns a 301.
Your RSS items and og:url still point at a starter-template placeholder like example.com or your-domain.com. Here is exactly where it leaks and how to fix every spot in one pass.
You moved domains but Search Console still tracks the old one, or the new property is empty. Migrate correctly with Change of Address without losing historical data.
One refresh the site loads, the next shows a hosting error or parking page. The real causes after binding a domain to a new host, and how to force every resolver onto the new record.
After a domain move, sitemap.xml still lists old-domain URLs and Search Console flags 'URL not allowed.' Find the stale site-URL config and fix it for good.
Your site is on HTTPS but the browser shows "Not fully secure." Diagnose which of 6 mixed-content cases you have and fix it for good — with current 2026 Chrome behavior.
Changed an A record but old caches won't expire? The TTL set BEFORE the change controls propagation. Diagnose your case and fix it the right way.
Both yourdomain.com and www.yourdomain.com load with a 200 and identical content. Why it splits SEO signals and the exact 301 fix per host.
Deploy a static Astro site to Firebase Hosting the right way: the firebase.json config, cache headers, clean URLs, and the SPA-rewrite trap that breaks your 404s.
Point your domain at Firebase Hosting with the exact TXT, A and AAAA records, dig verification commands, and fixes for the Needs setup loop and stuck SSL.
Point an apex + www domain at Vercel with the exact per-project DNS records, dig/curl verification, the CAA fix, and a Cloudflare-in-front setup that does not break SSL. Current as of June 2026.
A clear rule for when to buy a domain, plus 2026 registrar prices, WHOIS and trademark checks, and the day-one settings that prevent expensive regret.
Your host says A, a tutorial says CNAME, and the apex won't resolve or email broke. A web-verified cheat sheet for apex vs www vs subdomains (Vercel, Netlify, GitHub Pages, Cloudflare).
Updated DNS but the site shows the old IP or won't load? Verify with dig, check the active nameservers, flush local + browser cache, and wait out the TTL. Step-by-step, as of June 2026.
You changed DNS and some users see the new IP, some the old. Here's why regional inconsistency is normal, plus a measurable fix and verification path.
After a DNS change your MX disappeared and mail stopped arriving. Diagnose the exact case and restore the correct records for Google Workspace, Microsoft 365, Zoho, Fastmail, or Proton.
You bound a custom domain on Vercel / Firebase / Netlify but SSL stays "pending." Diagnose DNS, CAA, and Cloudflare-proxy causes and fix it fast.
Your apex domain works but blog.example.com gives NXDOMAIN or an SSL error. The fix is almost always a missing DNS row or a domain you forgot to attach at the host. Diagnose it in five buckets.
www.example.com works but example.com returns an error (or vice versa). Fix the missing DNS record, then add a 301 redirect to one canonical version.
A records point to an IP. CNAMEs point to another name. That one sentence solves most indie DNS confusion. Here is the other 10%, with exact Vercel, Firebase, and Netlify values.
"24 to 48 hours" is folklore. Modern DNS record edits go live in minutes. If yours hasn't after 30 minutes, something is misconfigured — here's how to prove which.
Root vs www is cosmetic until both serve the same content and split your SEO. Use this verified DNS table (Vercel, Firebase, Cloudflare), redirect config, and curl checks to lock it down in one pass.