Member Avatar for Dani

It's most likely on my end, but I can browse the web just fine, but for some reason I can't access either Facebook or Twitter?! I can do a google search, and no issues with any other sites I've tried browsing to so far.

I'm home, and not behind a proxy of any kind.

  • 3 Contributors
  • 5 Replies
  • 243 Views
  • 50 Minutes Discussion Span
  • Latest Post Latest Post by Dani

Dani AI

Generated

Noting that restarted a local DNS server and service while could reach Facebook from Vancouver and reported no problems, the symptom pattern points toward a regional resolver/peering problem rather than a global outage. The following focused checklist helps isolate whether the failure is a local DNS/resolver issue, an ISP/peering problem, or a wider CDN/BGP incident.

Quick diagnostic checklist (run in order):

  1. Verify name resolution locally and against a public resolver.

    nslookup facebook.com
nslookup facebook.com 8.8.8.8
dig @8.8.8.8 facebook.com +short

  2. Flush local caches (choose OS-appropriate command).

    ipconfig /flushdns                 # Windows
sudo dscacheutil -flushcache       # macOS (older)
sudo killall -HUP mDNSResponder    # macOS (many versions)
sudo resolvectl flush-caches       # Linux (systemd)
sudo service nscd restart          # Linux (nscd)

  3. Try a different path: a phone on cellular (Wi‑Fi off) or a VPN. If those work, the problem is upstream (ISP/resolver) not the site.

  4. Use traceroute to see where traffic stops.

    tracert facebook.com   # Windows
traceroute facebook.com # macOS/Linux

  5. Check the local hosts file for accidental blocks (C:\Windows\System32\drivers\etc\hosts or /etc/hosts) and ensure DNS forwarders on any home/AD server are reachable and not blocked on port 53.

  6. If changing the client to a public DNS (8.8.8.8 / 1.1.1.1) or using a VPN restores access, contact the ISP and report the outage with traceroute/nslookup output.

Notes and cautions: region-limited failures are commonly caused by misrouted BGP announcements, CDN/Anycast node problems, or ISP DNS/peering issues — resolving them usually requires ISP or CDN provider action. Avoid permanent changes to domain controllers or production DNS without backups and, when unsure, escalate to the ISP or the network/system administrator handling the home server.

Recommended Answers

All 5 Replies

Member Avatar for Dani

Hmm, seems to be a DNS issue on my end.

Member Avatar for leondegroot86

No problems here, good luck

Edited by leondegroot86
Member Avatar for Dani

OK so I restarted my domain / DNS server (it had some Windows updates) and I restarted my DNS service.

Facebook and Twitter still don't work for me.

I went to the website "Down For Everyone Or Just Me?" and it's telling me it's not just me. FB is down?!

Member Avatar for DavidB

I just logged on to Facebook no problem (from Vancouver, B.C., Canada).

I was able to get to twitter.com, but I don't have a Twitter account, so wasn't able to test further.

Edited by DavidB
Member Avatar for Dani

Looks like it's only affecting the United States right now.

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.