DNS Problems Explained: Fix Nameserver, Propagation & Record Errors (2026)

**DNS is the phonebook of the internet** — it translates your domain name into the server address where your site lives. When DNS breaks, everything breaks, even though your website itself is perfectly fine. It's the most misunderstood layer of web hosting and the cause of a huge share of "my site is down" tickets.

Here's how to understand it, diagnose it, and fix it.

The 5 Records You Actually Need to Know

Where DNS Lives: The Most Common Confusion

Your DNS is managed **wherever your nameservers point** — not necessarily your registrar, and not necessarily your host: - Nameservers at your **registrar** (default): registrar's DNS panel controls records - Nameservers set to **your host** (e.g., Patahost's `ns1/ns2.patahost.co.ke`): your host's cPanel Zone Editor controls records - Nameservers set to **Cloudflare**: Cloudflare controls everything

**Rule #1 of DNS debugging:** Find where your nameservers point. Edit records only there.

Common Symptoms & Quick Fixes

Symptom: "Site works for me but not my client" **Diagnosis:** DNS propagation — records were changed recently; global caches still hold old values. **Fix:** Wait 2–6 hours. Flush local caches: `ipconfig /flushdns` (Windows), restart router, test via mobile data. Check global propagation with `whatsmydns.net`.

Symptom: "Website fine, email completely dead" **Diagnosis:** MX record missing or pointing to the wrong server after a nameserver switch. **Fix:** In the authoritative DNS panel, verify the MX record points to `mail.yourdomain.co.ke` with Priority 10. Check cPanel Email Routing is set to **Local**.

Symptom: "www works but bare domain doesn't" **Diagnosis:** Missing A record for the root domain or missing CNAME for www. **Fix:** Ensure both an `A` record for `yourdomain.co.ke` and a `CNAME` for `www` exist pointing to the server.