Weird slow DNS resolution problem

[amgine]

I'm having some real annoying issues with all Microsoft OS's connecting to the web using dns addresses. Any time I reboot a machine, I have to ping the dns server directly an non-predetermined number of times before IE will finally be able to resolve DNS names. I have a linksys 8 port router with QOS turned off on roadrunner. This is starting to drive everyone in the house crazy, anybody got any ideas?

 

[amgine]

By the way, nbtstat -R, nbtstat -RR and ipconfig /flushDNS don't seem to make a difference and the machines are 98, ME, 2k, xP, and .net so its not operating specific, unless you want to start picking on MS

 

[amgine]

Bump for problem still not solved.....

 

[Saltin]

Are you using an ISP DNS server or your own?

 

[amgine]

ISP DNS servers are passed on to the client machines via the DHCP of the Linksys router

 

[Saltin]

Do you have the MTU set manually on your router?
Find out what the MTU of your ISP is and set it manually on the router. See if that improves performance.

You can either call your ISP and ask what the MTU is, or figure it out yourself with ping.

Just ping something like www.yahoo.com -l <size> -f
Make the size 1500 to start.
If it returns "paket needs to be fragmented but DF set", then lower your size untill it pings properly. You can use this method to determine the MTU exactly.
The highest size that pings properly is the MTU (i.e. 1470 works but 1471 says "paket needs to be fragmented....")

 

[amgine]

MTU turned out to be 1472 but I can't find a place to plug that in on the Linksys router config. Going to try a firmware upgrade next. Weird things is that if I log onto trillian or winmx first, I get connected, but if I try using IE, it takes like a half hour to finally get on. Thanks for the tips, let me know if you come up with anything else.