 | What's up with Frontier's DNS Servers???? I've been having extensive DNS resolution issues and did a traceroute tonight and see this:
traceroute to 74.40.74.40 (74.40.74.40), 64 hops max, 52 byte packets 1 192.168.168.1 (192.168.168.1) 3.473 ms 1.294 ms 1.140 ms 2 clsm-207-7-187-1-pppoe.dsl.clsm.epix.net (207.7.187.1) 15.296 ms 15.510 ms 14.983 ms 3 g8-1-rtr01-lkst.epix.net (216.37.197.113) 16.548 ms 16.304 ms 16.008 ms 4 216.37.155.193 (216.37.155.193) 16.558 ms 16.607 ms 15.986 ms 5 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 16.131 ms 16.346 ms 16.537 ms 6 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 16.550 ms 16.736 ms 15.951 ms 7 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 16.512 ms 17.039 ms 18.415 ms 8 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 16.544 ms 19.269 ms 16.456 ms 9 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.028 ms 16.412 ms 16.518 ms 10 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 16.923 ms 17.589 ms 16.959 ms 11 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.477 ms 17.527 ms 16.435 ms 12 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 16.934 ms 17.550 ms 16.900 ms 13 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.015 ms 16.490 ms 16.952 ms 14 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.017 ms 17.053 ms 16.969 ms 15 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 16.976 ms 17.052 ms 16.959 ms 16 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.751 ms 16.807 ms 17.497 ms 17 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 18.438 ms 16.933 ms 17.925 ms 18 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.445 ms 18.860 ms 17.047 ms 19 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.001 ms 17.885 ms 16.939 ms 20 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 19.373 ms 20.343 ms 17.427 ms 21 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.686 ms 17.387 ms 18.393 ms 22 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.524 ms 18.931 ms 17.433 ms 23 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.445 ms 17.539 ms 17.941 ms 24 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.505 ms 17.443 ms 18.003 ms 25 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.905 ms 18.880 ms 18.470 ms 26 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.442 ms 18.184 ms 17.456 ms 27 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.490 ms 17.536 ms 18.453 ms 28 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.962 ms 17.555 ms 18.401 ms 29 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 19.927 ms 18.026 ms 17.929 ms 30 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.993 ms 17.485 ms 26.530 ms 31 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.924 ms 18.505 ms 17.518 ms 32 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 17.933 ms 18.047 ms 18.465 ms 33 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.485 ms 18.516 ms 19.469 ms 34 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.906 ms 17.977 ms 17.937 ms 35 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 20.455 ms 20.301 ms 17.956 ms 36 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 19.149 ms 21.516 ms 22.275 ms 37 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 17.605 ms 20.883 ms 18.667 ms 38 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.466 ms 19.362 ms 17.944 ms 39 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 21.425 ms 18.300 ms 19.507 ms 40 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.649 ms 18.858 ms 18.934 ms 41 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 19.448 ms 18.322 ms 21.375 ms 42 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.933 ms 19.798 ms 20.861 ms 43 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 19.453 ms 18.920 ms 19.455 ms 44 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 19.454 ms 21.486 ms 18.979 ms 45 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 18.923 ms 22.284 ms 18.538 ms 46 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 19.228 ms 20.780 ms 18.963 ms 47 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 24.139 ms 19.901 ms 18.391 ms 48 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 20.455 ms 18.468 ms 24.219 ms 49 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 19.134 ms 20.718 ms 21.419 ms 50 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.937 ms 21.040 ms 20.057 ms 51 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 19.866 ms 18.555 ms 18.962 ms 52 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 24.368 ms 19.261 ms 19.926 ms 53 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 19.931 ms 22.404 ms 19.955 ms 54 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 20.133 ms 21.306 ms 20.947 ms 55 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 21.868 ms 18.815 ms 19.432 ms 56 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 21.403 ms 19.503 ms 19.467 ms 57 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 20.279 ms 20.832 ms 20.404 ms 58 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 19.421 ms 20.032 ms 22.611 ms 59 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 20.458 ms 20.564 ms 21.365 ms 60 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 18.888 ms 19.767 ms 22.404 ms 61 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 21.382 ms 19.385 ms 20.170 ms 62 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 20.393 ms 22.577 ms 21.355 ms 63 external.bigip01a.dlls.pa.frontiernet.net (199.224.64.133) 22.629 ms 22.045 ms 20.928 ms 64 server.sw02.dlls.pa.frontiernet.net (199.224.64.131) 20.397 ms 19.682 ms 20.379 ms |
|
 | Does your Internet still work? From the traceroute it looks like it never leaves frontiers pa center. It looks like it gets stuck in a loop. |
|
 | Yes... Internet works. We just experience random DNS lookup failures.
I've changed my DNS servers to Google's, so we'll see if that helps at all. |
|
 | I have been having issues today with my internet not working. I had been fighting with it for a while and then I ran a speed test. My download speed seemed ok, but hit various web sites it was really slow.
So I thought to myself maybe Frontier's DSN servers are screwed up... then I switch to Google's DNS servers and it started working fine again.
Out of curiosity I did a search and ended up at this post and I decided to reply.  |
|
 | Hence my request -
»[DSL] 7550 modem DNS server setting? -- Washington Island, Wisconsin across Death's Door Passage |
|
|
|
 tscs000 join:2012-10-11 New London, OH | reply to matthopp I was having the same issue with Frontier's DNS servers tonight. Changed the router to use OpenDNS addresses and everything is working fine now. |
|
 | Yes, please, how? |
|
 | reply to matthopp I'm having trouble in MI as well; have been for the last few days. I've tried power cycling and it didn't help. What a nuisance. |
|
 | reply to matthopp Does anyone have a solution? I haven't heard anything helpful from Frontier. |
|
 Reviews:
·Frontier Communi..
·WildBlue
| Follow the link above to change to OpenDNS 208.67.222.222 & 208.67.220.220
When the topic arises, speak up for a distributed DNS system. A convenient HOSTS file manager would be nice too so that one could maintain favorite name-IP redirects.
I'm no longer on a 'doze PC and so have lots to unlearn and learn. Fedora 18! -- Washington Island, Wisconsin across Death's Door Passage |
|
 MannusPremium join:2005-10-25 Fort Wayne, IN | reply to matthopp +1 for OPENDNS. |
|
 | I have had no issues in the 24 or so hours since getting rid of Frontier's DNS servers. -- Washington Island, Wisconsin across Death's Door Passage |
|
 | reply to matthopp The best solution, as marked here several times, is to not use Frontier's DNS servers. I have them marked as a fourth backup, with OpenDNS, Google DNS, and Level3 as the primary, secondary, and tertiary DNS servers, along with my internal DNS server.
A good deal of Internet trouble can be directly related to DNS issues. Web sites taking a long time to start loading but then load quickly is likely a DNS issue. Same with some content not loading at all. I suggest always using OpenDNS (208.67.220.220 and 208.67.222.222) GoogleDNS (8.8.8.8 and 8.8.4.4) and Level3 (4.4.4.4) instead of Frontier or any ISP. Comcast has their stuff together, so you could use them if you want. Can't change with AT&T because of their UVerse crap. -- CompTIA Net+ Network Administrator - I know networks! Professional Photographer - www.jnphoto.biz - Weddings and Senior Photos Nice and comfy with Frontier DSL: I can help with your issues! »speedtest.net/result/2472459013.png |
|
 | These are all fine solutions -- but what does it take to get Frontier to fix their network? |
|
 HankSearching for a new FrontierPremium join:2002-05-21 Burlington, WV kudos:1 | One thing that will eventually force Frontier to correct it is for customers to consistently file reports with Frontier, with their local controlling authority and with the FCC. Posting the issue in DSLReports does not constitute a filed report. |
|
 darciliciousCyber LibrarianPremium join:2001-01-02 Forest Grove, OR kudos:2 Reviews:
·Frontier FiOS
| said by Hank:One thing that will eventually force Frontier to correct it is for customers to consistently file reports with Frontier, with their local controlling authority and with the FCC. Say what? The FCC doesn't accept complaints about ISPs.
»www.fcc.gov/encyclopedia/faqs-in···omplaint -- ♬ Dragon of good fortune struggles with the trickster Fox ♬ |
|
 HankSearching for a new FrontierPremium join:2002-05-21 Burlington, WV kudos:1 4 edits | Understand, but they have accepted three complaints from me and required the ISP (Frontier) to respond. This may be because they are a telco supplying service via DSL. My complaints addressed only ISP related issues. I guess if one presents the issues without malice it gets people's attention.
But getting the complaints/issues on file is helpful getting issues resolved. One has to start with the carrier and if no response then address the local controlling or regulatory authority if the carrier habitually fails to resolve issues. |
|
 gozerPremium join:2010-08-09 Rochester, NY | reply to darcilicious All it says is that the FCC does not regulate ISP's or the inet. |
|
 darciliciousCyber LibrarianPremium join:2001-01-02 Forest Grove, OR kudos:2 Reviews:
·Frontier FiOS
| It says that in answer to the question:
How do I file a complaint against my Internet Service Provider?
If the FCC doesn't regulate something, than it has no power to enforce anything.
said by Hank:they have accepted three complaints from me and required the ISP (Frontier) to respond. I'd love to hear the exact details of this. Can you share them? Specifically, what was Frontier's "response"? -- ♬ Dragon of good fortune struggles with the trickster Fox ♬ |
|
 gozerPremium join:2010-08-09 Rochester, NY | My guess is that Frontier never responded to the FCC's request at all. As you stated they have little authority to force an ISP to respond. Remember when Frontier started pushing FIOS customers to drop FIOS tv by increasing the price. Well the FCC got complaints about this and even had some legal grounds to ask Frontier if this was their plan all along because the FCC had an agreement with Frontier based on them approving the Verizon acquisition. I think both the FCC and an attorney general sent this request and guess what Frontier never did answer at all. |
|