hayc59
VoodooChild
Premium
join:2001-02-26
David R.I.P. |  DNS problem again tonite!!!
this just plain sucks!! |
|
mtmra70
Premium
join:2001-03-22
Portage, MI | good thing you posted this thread |
|
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
 ·Comcast
| reply to hayc59
Snagged from Comcast.net Help Forums...
FOR WINDOWS XP, 2000, and 2003 ONLY
(credit goes to CajunTek for originally posting this for us).
To change DNS servers:
o Right click on the My Network Places icon on the desktop and select Properties. (If the icon is not available, go to Start menu | My Computer | My Network Places | View Network Connections.)
o Locate the network connection that is associated with your Internet connection. This is typically labeled something like "Local Area Connection." If you have more than one connection to choose from, be sure you determine the right one before proceeding.
o Right click on the appropriate connection and select Properties.
o In the list that appears under the General tab, double click on Internet Protocol (TCP/IP).
o In the window that appears, you want to select the option to Use the following DNS server addresses...
At this point you will want to enter at least one of your personal preferred DNS servers. There are a number of public servers suggested by members of the Comcast forum; simply do a search for 'DNS' and you should get adequate results.
o Press Ok out of all windows until you are back to the Network Connections window. You can now open your web browser and browse to a website to see if it connects faster.
ALWAYS USE PUBLIC SERVERS FIRST!!!! ... then as soon as the outage is resolved, flush your dns, and go back into your settings and reset it to Obtain DNS Automatically. It will get you back on your Comcast server.
Windows XP caches successful AND failed DNS lookups for 24hrs by default, so you want
TO FLUSH YOUR DNS
- Go to Start -> Run
- Type cmd ... click OK
- In the box that comes up, type ipconfig /flushdns ...press Enter key
Other Windows systems, simply rebooting should do the trick.
If you are using a router, power cycling it will usually clear out it's cache.
Public (Level3) Nameservers (these are NOT Verizon servers)
4.2.2.1
4.2.2.2
4.2.2.3
4.2.2.4
4.2.2.5
4.2.2.6
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
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
Sprintlink General DNS
204.117.214.10
199.2.252.10
204.97.212.10
Cisco
128.107.241.185
192.135.250.69 |
|
sortofageek
Premium,Mod
join:2001-08-19
Valhalla Dr
clubs:
2 edits | reply to hayc59
Let's keep this issue in this thread: »[DNS] 04-2005 Connection Problems - Discussion |
|
