 HankSearching for a new FrontierPremium
join:2002-05-21
Burlington, WV
kudos:1
3 edits | reply to gozer
Re: What's up with Frontier's DNS Servers???? Frontier did respond to the FCC with a copy of their response to me. They addressed what they were doing in our state to resolve the issues I raised. They were also happy to quote the amount of money that they had spent in our state. Please keep in mind that the majority of that money was spent in the capitol area and the surrounding counties. They have resolved many of the issues that I raised in my complaint.
From that complaint and Frontiers response I gained access to an individual in their management office. An individual that has been very helpful getting issues promptly resolved for me. She understand Frontiers issues pro's and con's, answering most questions honestly without hesitation and inconsistent or inaccurate information provided by the CSR's.
As I have mentioned several times in this forum when you are not getting resolutions to an issue you have to be persistent. When filing your complaint(s) you have to present them logically without being emotional. You will eventually get someone's attention. |
|
| reply to matthopp
Well as of this morning they've got something else going on. I have other DNS servers in, but as of this morning DNS isn't working at all... though I can ping IP addresses.
This is about ridiculous. |
|
HankSearching for a new FrontierPremium
join:2002-05-21
Burlington, WV
kudos:1 | Good morning Matthopp - What exactly are you seeing? When you ping are you entering an IP addrress? |
|
| reply to matthopp
Looks like it's actually a routing issue in their network this morning... joy.
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.168.1 (192.168.168.1) 1.634 ms 3.201 ms 1.323 ms
2 207.7.187.1 (207.7.187.1) 15.490 ms 15.525 ms 14.745 ms
3 74.43.38.25 (74.43.38.25) 17.757 ms 18.148 ms 16.428 ms |
|
| reply to matthopp
Let me try that again.
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.168.1 (192.168.168.1) 1.634 ms 3.201 ms 1.323 ms
2 207.7.187.1 (207.7.187.1) 15.490 ms 15.525 ms 14.745 ms
3 74.43.38.25 (74.43.38.25) 17.757 ms 18.148 ms 16.428 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * * |
|
|
|
| reply to matthopp
And now there is terrible latency from the DSLAM.
traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 52 byte packets
1 192.168.168.1 (192.168.168.1) 3.395 ms 1.164 ms 1.270 ms
2 clsm-207-7-187-1-pppoe.dsl.clsm.epix.net (207.7.187.1) 398.644 ms 408.892 ms 410.093 ms
3 g8-1-rtr01-lkst.epix.net (216.37.197.113) 511.454 ms 335.621 ms 380.538 ms
4 184.10.116.1 (184.10.116.1) 409.628 ms 408.967 ms 511.903 ms
5 ae3---0.cor01.asbn.va.frontiernet.net (74.40.5.29) 614.346 ms 409.090 ms 409.583 ms
6 ae1---0.cbr01.asbn.va.frontiernet.net (74.40.2.174) 307.171 ms 408.963 ms 307.176 ms
7 72.14.213.133 (72.14.213.133) 511.889 ms 24.287 ms 23.840 ms
8 216.239.46.250 (216.239.46.250) 41.713 ms 25.226 ms
216.239.46.248 (216.239.46.248) 25.396 ms
9 72.14.236.146 (72.14.236.146) 26.885 ms
72.14.236.98 (72.14.236.98) 73.326 ms
72.14.236.146 (72.14.236.146) 38.697 ms
10 72.14.238.18 (72.14.238.18) 26.689 ms
72.14.238.82 (72.14.238.82) 25.285 ms
72.14.238.18 (72.14.238.18) 25.225 ms
11 216.239.49.149 (216.239.49.149) 25.656 ms
72.14.232.21 (72.14.232.21) 40.306 ms
216.239.49.149 (216.239.49.149) 26.814 ms
12 google-public-dns-a.google.com (8.8.8.8) 29.215 ms 25.529 ms 25.080 ms |
|
HankSearching for a new FrontierPremium
join:2002-05-21
Burlington, WV
kudos:1 | Definitely looks like something is going on. |
|
gozerPremium
join:2010-08-09
Rochester, NY | reply to matthopp
have you tryed another pub dns service or just a trace to another one to see if you get same problem. But the timeing you are getting to the dslam is the real problem. Do a ping just to the first hop. This is a nice peramiter to use so you can run any comand from the run box and make the cmd window stay open "/k"
so "cmd /k ping -n 50 -w 1000 207.7.187.1"
Pinging 207.7.187.1 with 32 bytes of data:
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=62ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=43ms TTL=248
Reply from 207.7.187.1: bytes=32 time=40ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=75ms TTL=248
Reply from 207.7.187.1: bytes=32 time=57ms TTL=248
Reply from 207.7.187.1: bytes=32 time=41ms TTL=248
Reply from 207.7.187.1: bytes=32 time=50ms TTL=248
Reply from 207.7.187.1: bytes=32 time=76ms TTL=248
Reply from 207.7.187.1: bytes=32 time=92ms TTL=248
Reply from 207.7.187.1: bytes=32 time=78ms TTL=248
Reply from 207.7.187.1: bytes=32 time=65ms TTL=248
Reply from 207.7.187.1: bytes=32 time=46ms TTL=248
Reply from 207.7.187.1: bytes=32 time=51ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=46ms TTL=248
Reply from 207.7.187.1: bytes=32 time=47ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=39ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=38ms TTL=248
Reply from 207.7.187.1: bytes=32 time=41ms TTL=248
Reply from 207.7.187.1: bytes=32 time=51ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=43ms TTL=248
Reply from 207.7.187.1: bytes=32 time=72ms TTL=248
Reply from 207.7.187.1: bytes=32 time=55ms TTL=248
Reply from 207.7.187.1: bytes=32 time=64ms TTL=248
Reply from 207.7.187.1: bytes=32 time=80ms TTL=248
Reply from 207.7.187.1: bytes=32 time=48ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Reply from 207.7.187.1: bytes=32 time=45ms TTL=248
Reply from 207.7.187.1: bytes=32 time=65ms TTL=248
Reply from 207.7.187.1: bytes=32 time=37ms TTL=248
Ping statistics for 207.7.187.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 92ms, Average = 47ms |
|
| reply to Shadowesque
Forgive me for my lack of expertise. I have had issues, only with Frontier internet, with server timeouts on a Facebook game. Since it appeared to be a Frontier issue, I did a web search for help and found this forum. Can someone explain or give me some simple steps for this Frontier DNS bypass? I have a Mac and typically use Chrome for gaming only. I would be grateful for any assistance that can be provided. Thank you! |
|
HankSearching for a new FrontierPremium
join:2002-05-21
Burlington, WV
kudos:1 | Do you have FIOS or DSL? What type modem do you have? |
|
| well, there's where i am not an expert. lol. i assume it is DSL. i do not believe that FIOS is available yet in our area. we live in a small community and haven't had DSL very long. thank you for your response! |
|
HankSearching for a new FrontierPremium
join:2002-05-21
Burlington, WV
kudos:1 | OK, since you haven't had service for very long you probably have one of their newer modem models. Can you tell me what the number on the front panel is? May be something like 7500 or 7550? |
|
 NOYBSt. John 3.16Premium
join:2005-12-15
Forest Grove, OR
kudos:1 | reply to matthopp
People actually still using Frontier's redirecting DNS servers?
Thought I was the last hold out and I switched when they also enabled redirection on the what was previously their non-redirecting servers.
Using Level3, Google, and SpeakEasy DNS.
--
Be a Good Netizen - Read, Know & Complain About Overly Restrictive Tyrannical ISP ToS & AUP »comcast.net/terms/ »verizon.net/policies/
Say Thanks with a Tool Points Donation |
|
| reply to Hank
it is 7500. i apologize for the delay. had been traveling and just returned home. |
|
