| reply to File Quit
Re: ** 04/13/05 Connection Problems - Read first ** I'll put the numbers here again.:)
Verizon (Level3) Nameservers
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
SpeakEasy Nameservers
66.93.87.2
216.231.41.2
216.254.95.2
64.81.45.2
64.81.111.2
64.81.127.2
64.81.79.2
64.81.159.2
66.92.64.2
66.92.224.2
66.92.159.2
64.81.79.2
64.81.159.2
64.81.127.2
64.81.45.2
216.27.175.2
66.92.159.2
66.93.87.2
ORSC Public Access DNS Nameservers
199.166.24.253
199.166.27.253
199.166.28.10
199.166.29.3
199.166.31.3
195.117.6.25
204.57.55.100
Sprintlink General DNS
204.117.214.10
199.2.252.10
204.97.212.10
Cisco
128.107.241.185
192.135.250.69 |
|
|
|
 BlamPenguin PowerPremium
join:2002-02-06
Philadelphia, PA | reply to NOT
Re: ** 04/13/05 Connection Problems - Read first said by NOT:
Those would be the national DNS servers that won't work. Change to one of the DNS servers listed at the start of this thread.
My point was that the suggestion was in the post I was replying to (and someone else posted similar in this thread) that Comcast was starting to populate the DHCP servers wtih info that included the old local DNS servers for the time being. And my "test" was to show that this did not happen on my node.
I don't use their servers and they have nothing to do with my inability to get a connection, which I still believe is a routing problem that may relate to my CRAN, as this only started happening right around the time I was switched to it (~ 3 weeks ago). |
|
 sigPremium
join:2001-05-05 | reply to File Quit
Re: ** 04/13/05 Connection Problems - Read first ** Internet was out when I came home from work tonight in Sacramento, CA. Figured it was the same old, again. Logged on to dialup to check out the info here. Switched DNS servers and I'm cruising on broadband now.
BBR folks here just really, really rock, dontcha know.  |
|
| Re: ** 04/13/05 Connection Problems - Read first said by sig:BBR folks here just really, really rock, dontcha know. Maybe Comcast should cut Justin a check  |
|
 Big_DPremium
join:2003-06-02
Augusta, GA | reply to Blam
said by Blam:And my "test" was to show that this did not happen on my node. It may take some time (or perhaps not even make it to your node, who knows), but we do have a confirmed case here: »[DNS] Comcast reverted me to the old DNS servers.
--
You want the truth? You can't handle the truth! |
|
Big_DPremium
join:2003-06-02
Augusta, GA | reply to J D McDorce
said by J D McDorce:said by sig:BBR folks here just really, really rock, dontcha know. Maybe Comcast should cut Justin a check I think Justin should send Comcast a bill
--
You want the truth? You can't handle the truth! |
|
tshuee
join:2002-02-14
Indianapolis, IN | reply to J D McDorce
Indiana Down until 4am EST 4/14/05 I just got off the phone with Comcast tech support (So Called) they say that can't give out any DNS info as that is not the problem(BS).They "Claim" it's a migration issue with the Voip server. I asked how come I could hit a site via IP then and not by name. He said he wasn't sure and the only thing I could do would be to wait until the problem is resolved....
SO I dialed into my work and got on here and found the list of DNS ( THANK YOU ALL FOR POSTING THESE) and I'm off and running again!! For how long who knows ? |
|
Sbrav77Premium
join:2004-03-02
Bourbonnais, IL | reply to File Quit
Re: ** 04/13/05 Connection Problems - Read first Ditto here in Bourbonnais, Illinois. Another DNS issue. The second this week. Lets hope they get their act together. Also, I"m gonna print out the alternate dns list for future use. |
|
| reply to Blam
quote:
The little birdie was incorrect if the assumption was to not get the so-called national DNS servers.
I've got one of the new DNS addresses:
$ ping 68.48.0.12
PING 68.48.0.12 (68.48.0.12): 56 data bytes
64 bytes from 68.48.0.12: icmp_seq=0 ttl=245 time=13.227 ms
64 bytes from 68.48.0.12: icmp_seq=1 ttl=245 time=11.194 ms
64 bytes from 68.48.0.12: icmp_seq=2 ttl=245 time=11.963 ms
^C
--- 68.48.0.12 ping statistics ---
18 packets transmitted, 3 packets received, 83% packet loss
round-trip min/avg/max = 11.194/12.128/13.227 ms |
|
| reply to File Quit
Re: ** 04/13/05 Connection Problems - Read first ** 
Talked to Comcast about credit during the last fiasco the other day and they said to call back when it was restored to figure out the time for the credit. How the hell am I supposed to know when it is restored? I am not going to sit around and watch the stupid thing. Comcast has been ok but next outage a bunch of people in my area (Illinois)using Comcast are talking to SBC to get a deal to switch us all over to DSL. I doubt if Comcast cares but they will if enough people switch. |
|
BlamPenguin PowerPremium
join:2002-02-06
Philadelphia, PA | reply to Big_D
Re: ** 04/13/05 Connection Problems - Read first And someone else suggested that it may be due to who their previous providers were per this »I work for comcast |
|
Big_DPremium
join:2003-06-02
Augusta, GA | reply to flasic
said by flasic: I won't be trying it. :hmm: Could have been a fluke, or something bad between you and that DNS server, cuz I can ping it just fine and it is returning queries just as fast as DNS servers local to me.
--- 68.48.0.12 ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 28278ms
rtt min/avg/max/mdev = 30.442/30.638/30.905/0.250 ms, pipe 2
--
You want the truth? You can't handle the truth! |
|
 Jim GurdPremium
join:2000-07-08
Plymouth, MI | reply to File Quit
Alternate DNS Servers For several months I have been using alternate DNS servers and have had absolutely no connection problems.
For the primary I am using 66.93.87.2 which is Speakeasy and for the secondary I use 128.107.241.185 which is Cisco.
I have had them programmed into my router for a long time because Comcast has had a reputation for lousy DNS servers going back quite a while. In fact if I had not been reading these posts I would probably have never known that a problem existed. |
|
| reply to Time to go
Re: ** 04/13/05 Connection Problems - Read first ** I have done a little well alot of testing. Is from Chicago area and these DNS servers provide the fastest resoponse time here.
64.81.159.2 Chicago speakeasy
66.93.87.2 Seattle speakeasy |
|
| reply to File Quit
DHCP service is back near Boston, MA. Not sure if it's because they reverted the servers, or they've got the national ones back online.
When I called during the outage, I was informed that they couldn't give refunds while the service was out. [Incidentally, the first "account executive" I talked to couldn't give me a DNS server IP address ("We can't send all our customers to other companies"), but was happy to do an address translation for me. The address I asked for? www.broadbandreports.com.]
I just called, and they were now happy to give me some kind of credit for the outage. On the other hand, I asked about the IP addresses of their DNS servers, and the official "I talked to the supervisor and was informed to tell you this" response was, "we don't have IP addresses for that." 
Silly helpdesk. No cupcake for you. |
|
| reply to File Quit
Re: ** 04/13/05 Connection Problems - Read first Tri-Cities TN problems here as well.
Cable TV is out too
Comcast Sucks |
|
| reply to Big_D
said by Big_D:Could have been a fluke, or something bad between you and that DNS server, cuz I can ping it just fine and it is returning queries just as fast as DNS servers local to me. Still have packet loss to it, 65% to be exact. |
|
| reply to File Quit
Down here in Boston too..... |
|
 MortyPremium
join:2004-09-18 | Legacy Comcast markets have been reverted back to local DNS servers to reduce stress upon the national servers. No further information at this time. |
|
| said by Morty:Legacy Comcast markets have been reverted back to local DNS servers to reduce stress upon the national servers. No further information at this time. Thanks for the heads up Morty  !That makes sence i think.:) |
|
