Diagnosing intermittent "can't find IP" errors

  • Thread starter Thread starter DaveC426913
  • Start date Start date
  • Tags Tags
    Errors
Click For Summary
SUMMARY

The forum discussion centers on diagnosing intermittent "can't find IP" errors experienced by users while browsing various websites, primarily using Chrome on Windows 10. Users report sporadic DNS resolution failures, leading to error messages such as "server IP address could not be found." The consensus indicates that the issue is likely related to DNS server connectivity, with suggestions to check for hardware problems, potential interference from other devices, and to utilize tools like Wireshark for packet analysis. Users also recommend clearing browser caches and using alternative DNS servers like 8.8.8.8 to mitigate the issue.

PREREQUISITES
  • Understanding of DNS resolution processes
  • Familiarity with network troubleshooting tools such as Wireshark
  • Basic knowledge of browser cache management
  • Experience with speed testing and ping commands
NEXT STEPS
  • Learn how to use Wireshark for network packet analysis
  • Research methods for clearing browser cache effectively in Chrome
  • Explore alternative DNS servers and their configurations
  • Investigate common hardware issues that affect internet connectivity
USEFUL FOR

This discussion is beneficial for network administrators, IT support professionals, and anyone experiencing DNS-related connectivity issues while browsing the internet.

  • #31
Tom.G said:
suddenly PF didn't respond.
I've had the same sort of thing. I blamed the PF server but perhaps I was being hasty. At least it wasn't my Bank and PF can always wait without the World ending.
 
Computer science news on Phys.org
  • #32
You can always check this source for recent attacks. Sometimes, you see spikes on specific days.

https://www.akamai.com/us/en/resources/our-thinking/state-of-the-internet-report/web-attack-visualization.jsp

Here's data from the past week.
1574081910623.png

1574081975490.png


1574082070601.png
 
  • Like
  • Informative
Likes   Reactions: Klystron and Nik_2213
  • #33
You can filter the Akamai report. Here's one on power grid attacks last week (my personal interest)

1574082391941.png
 
  • #34
It's still happening but good to know there are likely external causes.

At least it wasn't PF, and my bank can always wait without the World ending. :-p
 
  • Like
Likes   Reactions: Nik_2213
  • #35
I recently had an intermittent DNS problem. My router has a setting to put a "The internet is down" page up when the internet is down. What it supposed to do is return an ip that the router can serve the error page on.

The IP was 10.0.0.1 or something close.

The problem is that the error page is not there and the all DNS entries gets cached and stuck on the non-existent server address. Ping to an IP address works just fine since the outages were seconds in duration. I found the answer on a 5 year old forum post. Just disable the completely broken "feature".

BoB
 
  • #36
Most of the time "site cannot be reached" or "unable to connect this site" come because of dns_probe_finished_nxdomain which means because of DNS. There can be many other reason as well
like you can try following steps
  1. Reboot your modem and Computer
  2. Reset chrome flags by resetting to default if your are using chrome
  3. Check your Host file, if the website you are opening is listed under host file you won't be able to connect
  4. flush your DNS
  5. Reset browser
You can read this article for brief troubleshooting steps on how to Fix dns_probe_finished_nxdomain
 
  • Like
Likes   Reactions: Tom.G and jedishrfu

Similar threads

  • · Replies 1 ·
Replies
1
Views
2K
  • · Replies 4 ·
Replies
4
Views
6K
  • · Replies 3 ·
Replies
3
Views
2K