How to fix ERR_NAME_NOT_RESOLVED error in WordPress and subdomain DNS setup

How to Fix “ERR_NAME_NOT_RESOLVED” on WordPress & Subdomains (Complete DNS Master Guide)

by

The error ERR_NAME_NOT_RESOLVED means your web browser cannot map the requested domain or subdomain (e.g., server.yourdomain.com) to a valid server IP address via DNS lookup. To fix this in WordPress, either point an A Record (or CNAME) for that hostname to your server’s public IP inside your DNS Zone Editor, flush your local OS DNS cache (ipconfig /flushdns), or remove incorrect redirect rules in .htaccess and wp-config.php that force traffic to an unmapped subdomain.

Website develop karte waqt ya WordPress migration ke baad sabse irritating screen hoti hai jab browser display karta hai: “This site can’t be reached – server IP address could not be found (ERR_NAME_NOT_RESOLVED)”.

Yeh error tab aata hai jab client browser internet ke Domain Name System (DNS) se poochta hai ki is domain ka computer server kahan hai, aur DNS server jawab deta hai: “Yeh record meri registry mein exist hi nahi karta.”

Khaaskar jab aap cPanel me subdomains create karte hain, staging setups banate hain, ya .htaccess aur wp-config.php ke zariye automated redirects lagate hain, toh ek single missing A Record ya misconfigured URL pura setup break kar deta hai.

Is exhaustive engineering guide me hum ERR_NAME_NOT_RESOLVED ka technical workflow, root causes, aur 6 step-by-step verified fixes dekhenge.

Technical Anatomy: How DNS Lookup Actually Fails

Jab aap browser me [https://agmhost.com](https://agmhost.com) ya koi subdomain (jaise server.agmhost.com) enter karte hain, background me ek multi-step recursive resolution process shuru hota hai:

[Browser Request: server.yourdomain.com]
                  │
                  ▼
         1. Local DNS Cache (PC / Router) ──► [Not Found]
                  │
                  ▼
         2. Recursive Resolver (ISP / 8.8.8.8) ──► [Queries Root Server]
                  │
                  ▼
         3. TLD Nameservers (.COM / .IN) ──► [Points to Authoritative NS]
                  │
                  ▼
         4. Authoritative Nameserver (Cloudflare / cPanel Zone)
                  │
                  ├──► Record Found (A Record -> 103.x.x.x) ──► [HTTP Handshake Success]
                  │
                  └──► Record Missing (No A/CNAME Entry)   ──► [ERR_NAME_NOT_RESOLVED]

Agar Authoritative Zone File ke andar us particular hostname ka valid A Record (IPv4 address) ya CNAME map nahi hai, toh resolution process fail ho jata hai aur browser ERR_NAME_NOT_RESOLVED (ya Firefox/Edge me DNS_PROBE_FINISHED_NXDOMAIN) throw karta hai.

The 4 Primary Root Causes Behind the Error

  1. Unregistered or Missing Subdomain DNS Record: Subdomain cPanel me create toh ho gaya, lekin authoritative DNS provider (jaise Cloudflare ya external registrar) me uska A record add nahi hua.
  2. WordPress URL Mismatch (Redirection Loop): Database (wp_options) ya core config me WP_HOME galat subdomain par set hai jo physically exist nahi karta.
  3. Stale Local DNS Cache: Server par IP change hone ke baad aapka computer ya local WiFi router purani invalid IP cache hold karke baitha hai.
  4. Faulty .htaccess Redirection Rules: Rewrite rules kisi unmapped host prefix par traffic force kar rahi hain.

Method 1: Verify & Add DNS Records in cPanel (Zone Editor)

Agar aap cPanel use kar rahe hain aur error kisi subdomain par aa raha hai:

  1. Apne hosting control panel (cPanel) me login karein.
  2. Search bar me type karein Zone Editor (Domains section ke andar).
  3. Apne primary domain ke bagal me Manage button par click karein.
  4. Filter me A Record select karein aur check karein:
    • Kya wahan aapke subdomain ka record hai? (e.g., server.agmhost.com).
  5. Agar record missing hai:
    • Click Add Record.
    • Name: subdomain (e.g., server.yourdomain.com).
    • Type: A
    • TTL: 14400 (ya 300 fast testing ke liye).
    • Record (IP Address): Apne web server ka exact Public Shared/Dedicated IP address enter karein.
  6. Click Save Record.

Method 2: If Using Cloudflare (The Orange Cloud Proxy Trap)

Agar aapki website ke nameservers Cloudflare par pointed hain, toh cPanel me changes karne se DNS update nahi hota:

  1. Apne Cloudflare Dashboard me login karein.
  2. Domain select karein aur DNS > Records tab me jayein.
  3. Check karein ki target hostname wahan listed hai ya nahi.
  4. Click Add Record:
    • Type: A
    • Name: Subdomain prefix (e.g., server ya @ root ke liye).
    • IPv4 address: Hosting server IP.
    • Proxy status: Initial setup ke waqt isko DNS Only (Grey Cloud) par rakhein taaki SSL propagation aur direct server connectivity verify ho sake.
  5. Save karein.

Method 3: Correct Hardcoded WordPress URLs in wp-config.php

Aksar jab theme ya server error throw hota hai (jaise humne PHP 8 create_function guide me dekha tha), log site recovery ke chakkar me galat home URLs inject kar dete hain jo non-existent subdomains par point kar dete hain.

Is silent redirection ko override karne ke liye:

  1. Hosting File Manager me jayein aur public_html/wp-config.php ko edit karein.
  2. Line /* That's all, stop editing! Happy publishing. */ ke theek upar check karein ki koi invalid URL toh define nahi hai.
  3. In do lines ko strictly correct domain ke sath verify karein:

PHP

define('WP_HOME', 'https://agmhost.com');
define('WP_SITEURL', 'https://agmhost.com');
  1. File save karein. Yeh rule database entries ko bypass karke direct standard domain par site load karwayega.

Method 4: Flush Stale Local DNS Cache & Socket Pools

Agar server-level par DNS setup sahi hai lekin aapke machine par error persist kar raha hai, toh local resolver cache ko clear karein:

Windows Command Prompt (CMD):

Open CMD as Administrator and execute:

DOS

ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew

Browser Socket Cache Flush:

Chrome, Opera ya Brave browser me DNS cache browser memory me bhi store hoti hai:

  • Address bar me enter karein: chrome://net-internals/#dns (Opera ke liye: opera://net-internals/#dns).
  • Click karein “Clear host cache”.
  • Phir jayein: chrome://net-internals/#sockets aur click karein “Flush socket pools”.

Method 5: Reset Corrupted .htaccess Rules

Agar koi third-party security plugin ya redirection rule website ko loop me bhej rahi hai:

  1. File Manager me public_html/.htaccess file ko rename karke .htaccess_backup kar dein.
  2. Nayi blank .htaccess file create karein aur standard WordPress rules paste karein:

Apache

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
  1. Save karein aur website ko Incognito window me load karke check karein.

Method 6: Switch to Reliable Public DNS Resolvers

Agar aapke local internet service provider (ISP) ke DNS servers out of sync hain aur worldwide propagation catch nahi kar pa rahe:

ProviderPrimary IPv4 DNSSecondary IPv4 DNSKey Advantage
Cloudflare DNS1.1.1.11.0.0.1Fastest global propagation (sub-15ms)
Google Public DNS8.8.8.88.8.4.4Unmatched reliability and index awareness
Quad9 DNS9.9.9.9149.112.112.112Built-in malicious domain blocking

Apne computer ya Wi-Fi router ke IPv4 settings me jakar DNS ko 1.1.1.1 aur 8.8.8.8 par switch karein taaki zero-latency lookup ensure ho sake.

Real-Time DNS Propagation Checkers

DNS records update karne ke baad duniya bhar ke root servers tak new IP replicate hone me 15 minutes se 24 hours lag sakte hain. Propagation progress track karne ke liye tools use karein:

  • whatsmydns.net: Global map par check karta hai ki aapka domain globally resolve ho raha hai ya nahi.
  • DNSChecker.org: Specific record types (A, CNAME, MX, TXT) ka worldwide resolution status display karta hai.

Reliable Infrastructure Prevents DNS & Host Dropouts

Low-tier shared hosts ke DNS nameservers aksar high latency aur periodic timeout dropouts face karte hain, jisse visitors ko intermittent DNS resolving errors dekhne ko milte hain.

Agar aap enterprise Anycast DNS architecture, 99.99% uptime redundancy, aur ultra-fast NVMe cloud servers chahte hain, toh explore karein AGM Web Hosting India ke robust cloud solutions.

Frequently Asked Questions (MEGA FAQ)

1. ERR_NAME_NOT_RESOLVED aur DNS_PROBE_FINISHED_NXDOMAIN me kya fark hai?

Dono identical errors hain. ERR_NAME_NOT_RESOLVED Chromium-based browsers (Chrome, Edge, Opera) ka error code hai, jabki NXDOMAIN (Non-Existent Domain) raw DNS protocol response code hota hai.

2. DNS record add karne ke baad kitni der me site open hogi?

Agar TTL (Time to Live) 300 seconds set tha, toh changes 5–10 minutes me propagate ho jate hain. Default ISP caching ki wajah se maximum 2 se 24 ghante tak lag sakte hain.

3. Kya SSL certificate expire hone se ERR_NAME_NOT_RESOLVED aa sakta hai?

Nahi. SSL expire hone par ERR_CERT_DATE_INVALID ya Privacy warning aati hai. ERR_NAME_NOT_RESOLVED pure network level DNS failure hai jo IP resolve na hone par aati hai.

4. Subdomain cPanel me add kiya par site fir bhi nahi chal rahi, kyu?

Agar aapka main domain Cloudflare nameservers par chal raha hai, toh cPanel me subdomain add karne par automatically Cloudflare me record nahi banta. Cloudflare DNS me manual A Record add karna zaroori hai.

5. CNAME Record aur A Record me kya fark hota hai?

A Record domain ko direct IP address (e.g. 192.0.2.1) par map karta hai. CNAME Record ek hostname ko doosre hostname par point karta hai (e.g. blog.domain.com pointing to domain.com).

6. Mobile phone par site open ho rahi hai par PC par nahi, iska kya matlab hai?

Iska matlab hai ki server side par DNS record live ho chuka hai, lekin aapke PC ke operating system ya local router me stale DNS cache bacha hua hai. Local DNS flush karein.

7. Kya VPN use karne se ERR_NAME_NOT_RESOLVED theek ho sakta hai?

Agar error sirf aapke local ISP ke DNS server failure ki wajah se tha, toh VPN enable karne par site instantly load ho sakti hai kyunki VPN apna dedicated external DNS tunnel use karta hai.

8. wp-config me WP_HOME change karne ke baad dashboard login nahi ho raha?

Ensure karein ki aapne URL ke end me trailing slash (/) na lagaya ho, aur HTTP/HTTPS protocol sahi se mention kiya ho.

9. Dynamic DNS kya hota hai?

Dynamic DNS (DDNS) un users ke liye hota hai jinka residential IP address badalta rehta hai. Commercial web servers ko hamesha Static Dedicated Public IP par A record map karna chahiye.

10. Kya LiteSpeed Cache is error ko solve kar sakta hai?

Nahi. Jaise humne hamare LiteSpeed Cache analysis me dekha tha, caching application aur web-server layer par kaam karti hai. DNS resolution network layer par browser level par hoti hai.

Verdict & Final Summary

ERR_NAME_NOT_RESOLVED server-side DNS absence ya client-side resolver corruption ka signal hota hai. Isko theek karne ka sabse fast rasta hai: cPanel Zone Editor ya Cloudflare me A record verify karein, wp-config.php ke home URLs check karein, aur terminal se local DNS cache ko flush karein.

Leave a Comment