On Monday I discovered I could not get to certain websites -- common ones such as aol.com and networksolutions.com. All other sites were fine.
VZ call center reps said there must be a server out "somewhere." Problem resolved itself a few hours later.
Today, the same thing is happening, with the same sites.
Anyone have any ideas what or where the problem may be? Is this likely to be VZ server issues (flukey server at CO) or somewhere else? Having the same problem intermittently two out of three days suggests it's not a problem with my equipment or settings.
That sounds like a DNS issue at Verizon. DNS is that piece of the web infrastructure that converts the familiar URL, such as aol.com, into it's IP address, or 64.12.50.151 . You could try reconfiguring your router to use someone other than Verizon for DNS lookup. Try doing a little research on open DNS.
If it is any consolation, I frequently had the same problem you are experiencing at my prior business address when using Verizon DSL. We could reach sites like Google or Yahoo, but not our own site or CNN. This would be an intermitent problem, exactly as you describe. Switching to Open DNS solved that problem once and for all.
I agree with astro_guy. I switched to OpenDNS a year or so ago and have been very pleased. With Verizon's DNS servers, they would work fine, then suddenly I could not get to some sites, wait a while and they might work again, and occasionally could not get to any sites. Have not had a single issue since switching to OpenDNS. Plus OpenDNS offers some optional filters for avoiding porn and stuff, potentially very useful of you have kids around. And it is FREE (although they do offer some additional services for a fee).
__________________________________
Justin
Verizon FiOS TV, Internet, and phone
QIP6416-P1, IMG 1.7C, Build 09.83
Keller, TX 76248
If it is would have been a DNS issue, it won't open any webpages.
Try doing a Traceroute to the website and please post the results.
For windows:
for ex
C:\>tracert www.website.com
Thanks for the responses. It's happening again today. Seems to be timing out at different points. Any ideas? Wouldn't be a huge issue except for the fact that Network Solutions is my email host.
C:\Users\JG>tracert www.networksolutions.com
Tracing route to www.networksolutions.com [205.178.187.13]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 6 ms L100.NWRKNJ-VFTTP-119.verizon-gni.net [72.88.205.1]
3 7 ms 6 ms 7 ms G5-0-7-1719.NWRKNJ-LCR-07.verizon-gni.net [130.81.131.124]
4 10 ms 7 ms 6 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
5 12 ms 13 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
6 11 ms 10 ms 10 ms 204.255.168.90
7 10 ms 10 ms 10 ms cr2-tengig-0-15-4-0.NewYork.savvis.net [204.70.198.17]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
etc.
C:\Users\JG>tracert www.aol.com
Tracing route to www-east.aol.com.aol.akadns.net [64.12.244.203]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms L100.NWRKNJ-VFTTP-119.verizon-gni.net [72.88.205.1]
3 7 ms 7 ms 6 ms G5-0-7-1719.NWRKNJ-LCR-07.verizon-gni.net [130.81.131.124]
4 7 ms 6 ms 7 ms so-5-0-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.29.8]
5 12 ms 11 ms 12 ms so-12-0-0-0.NY325-BB-RTR1.verizon-gni.net [130.81.17.6]
6 24 ms 19 ms 16 ms 204.255.168.58
7 10 ms 10 ms 10 ms bb2-new-p2-0.atdn.net [66.185.152.158]
8 11 ms 11 ms 10 ms bb1-new-p0-0.atdn.net [66.185.152.192]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
etc.
Just try configuring your router to use Open DNS instead of Verizon's DNS. I am confident that this will solve your problem.
Hello ReputationDoc,
Sorry for the delayed response. In order to get to the bottom of this we are going to need to get a Tech out to your location and have him run Tracert directly out of the ont. Most likely the router is not the issue, but before our IT Dept will start to work this issue, that needs to be confirmed. Please pm me when a good date and time ( am or pm) appointment would be. I am also posting this reply in your post in Verizon direct. Thanks
Astro Guy -- Just happened again. Flipped quickly to Open DNS. Same problem.
Also just had an episode where I couldn't get to any site...yet IP phone through same router worked fine. ?????
Finally, when everything seemed to come back (back on VZ DNS) I went to networksolutions.com (my email host) and got there fine. Ran a tracert out of curiosity and timed out on a Savvis server in Washington, DC. Why would the tracert fail on a domain that I can access?
Anyone have any other ideas here?
VZ Direct seems to only respond on a 24-48 hour cycle. I've had two more outages where I can't get to sites but still have Internet connection.
The tech I was told had to come and "run tracert from the ONT" came and said he had no idea what that means. Said if my IP phone system is working the problem's not here.
Anyone? Anyone? Bueller?
@ReputationDoc wrote:Anyone have any other ideas here?
VZ Direct seems to only respond on a 24-48 hour cycle. I've had two more outages where I can't get to sites but still have Internet connection.
The tech I was told had to come and "run tracert from the ONT" came and said he had no idea what that means. Said if my IP phone system is working the problem's not here.
Anyone? Anyone? Bueller?
Well the tracert will time out on non responsive routers. That could mean that the router is down OR that the router is programmed not to respond. Doesnt necessarily mean that the router is down, could simply be a router that doesnt respond.
As for running a tracert from the ONT. In this case it is not needed. You can plainly see that from your tracert's that the signal makes it out past the Verizon network before failing. And since you were doing this while you were having an issue, the problem is not likely a Verizon issue.
Like the tech support agent told you, there is likely a router out there that is having issues, most of these will self correct after a time. (as you've seen) Now unfortunately, unless you can find out what the router is that is failing and who it belongs to, there is not much that can be done.
Also DNS will not be an issue in your case as the tracert shows that when you type in the address it knows where to go. It makes it out onto the internet and then drops. This means that the computer knows where to go. It navigates the Verizon network just fine, hits the internet, and then gets lost on one of the routers. Meaning that either the last router to respond has a bad route and is sending you to oblivion. Or the next router in the sequence is down and not responding.
Start a new topic or ask questions in the open forum.
