it just happened that one day when I am about to log into facebook page it says that facebook.com’s server DNS address could not be found. So i checked the computer setting if they blocked this page but it is not, what could be the problem of this.

Dani AI

Generated

Short summary and a compact troubleshooting plan based on ’s error and ’s suggestion to check DNS settings.

Common causes: a stale DNS cache, an edited hosts file that blocks facebook, router/ISP DNS problems or filtering, a browser extension/proxy/VPN interfering, or malware that hijacks DNS. Narrow the scope first by checking whether the problem is the PC, the router, or the ISP.

Quick, ordered checks (run until one shows the cause):

  1. Verify it’s not the router/ISP: try the same site from another device on the same Wi‑Fi and from your phone using cellular data.

  2. Clear local caches and reset the Windows network stack, then reboot: run the flush and reset commands below (open an admin command prompt).

    ipconfig /flushdns
    netsh winsock reset

    Reboot then test again.

  3. Basic reachability and path checks (these show whether the name resolves to an IP and where traffic stops):

    ping facebook.com
    tracert facebook.com
  4. Check the hosts file (Windows path shown so you can inspect it). If there is any line mapping facebook domains to 127.0.0.1 or other IPs, remove or comment it out and save a backup first:
    C:\Windows\System32\drivers\etc\hosts

  5. Rule out browser/extensions/proxy: test in a fresh private window with extensions disabled or try a different browser. Disable any VPN or proxy temporarily.

  6. If the name fails only on your PC but other devices work, try setting a well-known public DNS on your PC or router temporarily (Cloudflare/Google/OpenDNS) to see if resolution succeeds. If those resolve facebook but your normal DNS does not, the issue is the configured DNS server or ISP filtering.

If the problem persists, post the DNS server addresses your PC is using, plus the outputs of the ping and tracert above and whether other sites resolve. That information will make it possible to pinpoint whether the failure is local, at the router, or with the ISP.

Recommended Answers

All 3 Replies

Check your current DNS settings. From a command prompt with 'ipconfig /all' . What are your dns servers?

Once you have dns IPs, use nslookup to check.

nslookup
www.google.com
<you should get an answer here with IPs, if you don't, your DNS servers are wrong>
server 8.8.8.8
www.google.com
<you should get IPs here, if you don't, your outbound access is having issues going to 8.8.8.8>

Thank you so much pal :D

Did it work? Status?

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.