ATT Guy2
join:2002-07-09
Aurora, IL | Re: It's sad... All I have to say is Thank You for the alternate DNS server...I just plugged them in and back on the net. | |
|
 
File Quit
Mac Geek
Premium
join:2002-11-28
| Re: It's sad... On behalf of the techies here that proposed the solution, your welcome. I was just relaying information from past outages and FAQ posts.
--
Apple rules!!! Get an iPod and iBook today, what's to lose? »www.apple.com | |
|
Nerdtalker
Working Hard, Or Hardly Working?
Premium,MVM
join:2003-02-18
Tucson, AZ
clubs: | I just use 4.2.2.1, 4.2.2.2, and 4.2.2.3, I haven't used Comcast's DNS servers for at least 2 years or so. | |
|
 | 
DHRacer
Fire Survivor
join:2000-10-10
Lake Arrowhead, CA | Re: It's sad... Is there some reason why you use Verizon's LA DNS servers (besides the fact that Comcast's DNS Servers don't work)?
Why not other Comcast DNS servers they might have? | |
|
| |
Nerdtalker
Working Hard, Or Hardly Working?
Premium,MVM
join:2003-02-18
Tucson, AZ
clubs: | Re: It's sad... The verison ones have always been faster for me.  | |
|
| | | 
jansm38
Vn800-B
Premium
join:2003-05-19
Blackwood, NJ
| Re: It's sad... I use Comcast as the Primary and 4.2.2.2 as the secondary.
I never noticed any outage since most of my page requests were already cached in XP and anything new went to the Secondary. There may have been a slight delay while waiting a second or two for the Comcast DNS request to time out.
It's generally not a good idea to use someone elses DNS server as your Primary as it's putting an extra unanticipated load on them. When they do their requirements forcasting they only use their own customer base in the equation, they're not considering the load of a few million extra requests coming from the Comcast network. What could end up happening if the load gets to be too much is the other DNS host could block requests from anyone not on their network, that would be a bad thing. | |
|
|
|
|
