Diagnosing intermittent "can't find IP" errors

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

Discussion Overview

The discussion revolves around diagnosing intermittent "can't find IP" errors experienced by a user while browsing various websites. The scope includes troubleshooting connectivity issues, potential DNS problems, and various factors that may contribute to the errors.

Discussion Character

  • Exploratory
  • Technical explanation
  • Debate/contested

Main Points Raised

  • One participant describes experiencing sporadic errors when trying to access websites, suggesting a possible DNS issue as the server names are not resolving to TCP/IP.
  • Another participant proposes that the problem could be related to a broken internet connection or a slow connection causing timeouts, listing various potential causes such as damaged wires or interference from streaming activities.
  • Some participants mention that the errors occur almost immediately, indicating a possible caching issue with the browser rather than a standard timeout.
  • Several participants share personal anecdotes about past connectivity issues related to physical damage to cables, including water damage and animal interference.
  • One participant humorously suggests that the issue might be an ageist conspiracy by Facebook against the original poster.
  • Another participant notes that if the problem were local, it should be reflected in speed tests, which show normal throughput.

Areas of Agreement / Disagreement

Participants express multiple competing views regarding the cause of the errors, with no consensus reached on a single explanation. Some focus on DNS issues, while others consider physical connectivity problems or external factors.

Contextual Notes

Participants mention various potential causes for the errors, including physical damage to cables, network congestion, and issues with DNS resolution. However, there are unresolved assumptions about the nature of the user's connection and the reliability of their speed tests.

  • #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

Is a VPN required for a WiFi hotspot meant only for a home?
  • · Replies 1 ·
Replies
1
Views
2K
ISP can tell what my internal network ip's are?
  • · Replies 4 ·
Replies
4
Views
6K
Troubleshooting Internet Problems: Can't Find Server
  • · Replies 3 ·
Replies
3
Views
2K