I am experiencing frequent DNS failures. No matter whether I use the Verizon servers, Google servers, Level3 servers or any DNS server, I get frequent DNS lookup failures.
Pinging the IP of the server will result in a "Destination Net Unreachable" error. (see below)
I have this problem on a Linux computer, a Windows 7 computer, a Windows XP computer, an Adroid phone, an iPhone, Kindle and an Android tablet.
I do not experience this problem if I take these computers to my work which uses Cox as the ISP.
I have rebooted the Verizon-supplied router several times with no improvement
$ping 151.199.0.30
PING 151.199.0.39 (151.199.0.39) 56(84) bytes of data.
From 192.168.1.1 icmp_seq=14 Destination Net Unreachable
64 bytes from 151.199.0.39: icmp_seq=20 ttl=250 time=22.6 ms
...
--- 151.199.0.39 ping statistics ---
57 packets transmitted, 38 received, +1 errors, 33% packet loss, time 56051ms
rtt min/avg/max/mdev = 20.826/23.462/28.066/1.816 ms
@hoytduff wrote:I am experiencing frequent DNS failures. No matter whether I use the Verizon servers, Google servers, Level3 servers or any DNS server, I get frequent DNS lookup failures.
Pinging the IP of the server will result in a "Destination Net Unreachable" error. (see below)
I have this problem on a Linux computer, a Windows 7 computer, a Windows XP computer, an Adroid phone, an iPhone, Kindle and an Android tablet.
I do not experience this problem if I take these computers to my work which uses Cox as the ISP.
I have rebooted the Verizon-supplied router several times with no improvement
$ping 151.199.0.30
PING 151.199.0.39 (151.199.0.39) 56(84) bytes of data.
From 192.168.1.1 icmp_seq=14 Destination Net Unreachable
64 bytes from 151.199.0.39: icmp_seq=20 ttl=250 time=22.6 ms
...--- 151.199.0.39 ping statistics ---
57 packets transmitted, 38 received, +1 errors, 33% packet loss, time 56051ms
rtt min/avg/max/mdev = 20.826/23.462/28.066/1.816 ms
If a ping directly to the IP Address is failing, then it's not a DNS issue. Pinging the IP Address bypasses the DNS lookup. I would recommend that you contact Verizon via one of the options on their Contact Us page, and see if tech support can't run some tests.
All connected by Cat-5.
It's not a DNS lookup failure per se, but a failure to actually reach the DNS server in the first place as you can see. That causes any lookup to timeout and the browser just fails to connect to the site.
Since my hardware works OK when it's not on the local network, I'll contact Verizon support and deal with that anguishly terrible experience.
Start a new topic or ask questions in the open forum.
