View Full Version : Horrible DNS issue.
Nine
June 6th, 2006, 12:55 AM
Alright I've been having this problem for over a month now.
Basically it takes a really long time to resolve domains. Like, 3 or 4 retries.
It's only my computer because none of the other computers on the network have this problem.
My NIC is built into my Abit NF7 motherboard.
I tried formatting and installing windows again but that didn't fix it.
http://www.choppeduphooker.com/files/netsettings.jpg
here are my internet settings (they're all default as far as i know.)
i have one last idea - another port on the router. i doubt it will work so i'll post this anyway.
Nine
June 6th, 2006, 01:40 AM
i tried a different port and it didnt fix the problem.
marden
June 6th, 2006, 06:09 AM
Did you try another cable?? Could be the one that you're using is fubar.
Nine
June 6th, 2006, 12:17 PM
Honestly I don't think that's the issue. That wouldn't really affect my ability to resolve domains, and if it did.. it would affect a lot of other things.
Nine
June 8th, 2006, 02:20 PM
:(
adamantium
June 8th, 2006, 06:49 PM
If this isn't the case already, try statically entering in your ISP's DNS servers or server into the router. Maybe that computer is just having problems resolving the host.
Nine
June 8th, 2006, 06:58 PM
My router picks them up automatically.
adamantium
June 8th, 2006, 07:06 PM
If you are this desperate and willing, I'd try getting the DNS server addresses from your ISP and entering them in statically. I work for my ISP and I've seen a few cases where the DNS entries refuse to resolve unless the servers have been entered statically. Weird shit, and it's a long shot, but if you've exhausted all your other options I'd try it.
Nine
June 8th, 2006, 07:31 PM
Are you still talking about my router?
Or windows?
adamantium
June 8th, 2006, 07:39 PM
Router. May want to try bypassing the router and going directly into the modem and entering the DNS servers into your machine as well though. Can't hurt to try.
Nine
June 8th, 2006, 09:54 PM
Bypassing the router didn't work. With and without the DNS servers manually entered in windows.
Putting the ips in as static in the router didn't work either. :(
MastaFlex
June 9th, 2006, 02:00 AM
start -> run -> cmd
ipconfig /flushdns
Try that.
Nine
June 9th, 2006, 11:24 AM
lol I've done that so many times.
Each time I try something I do that.
adamantium
June 9th, 2006, 05:25 PM
Next time I work I will ask some of the more experienced guys up there if they have any ideas. I don't work for another three days though, so you might not want to wait that long.
Nine
June 9th, 2006, 09:43 PM
It's been months so 3 more days won't hurt.
Thanks.
MitsuMan
June 11th, 2006, 01:04 PM
What ISP are you on?
You have to consider that maybe their domain name servers are whacked for everyone. Here are some that I use and know work:
Bellsouth
205.152.144.235
205.152.37.254
AT&T
24.88.1.66
24.88.1.67
Mindspring
207.69.188.186
207.69.188.185
While you will want to find one with the shortest trip time to you for the longrun, these will at least work for testing.
Nine
June 11th, 2006, 01:07 PM
- no one else connected to the router has this problem
- no one else on my isp has the problem
- no other dns servers work
illskillz
June 11th, 2006, 09:09 PM
have you tried another nic card?
MitsuMan
June 11th, 2006, 11:29 PM
have you tried another nic card?
try it
Nine
June 12th, 2006, 11:37 AM
I don't have any spares at the moment, but I'll see if I can borrow one.
It would really piss me off if that was the problem. I've had it in the back of my mind the whole time but I never really wanted to find out that my motherboard was starting to go.
adamantium
June 13th, 2006, 04:54 PM
Everyone up here (where I work) is pretty sure your NIC card is the problem. :/
Nine
June 13th, 2006, 06:38 PM
:'(
vBulletin® v3.7.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.