🚀 go-pugleaf

I found a better solution (and the reason why we need a solution at
all) regarding the recent DNS problems. As it turns out, AT&T *is*
actually serving up DNS!! Problem is, they're changing which server is
doing this *very* often - much more often than Windows 2000 or XP
expects it. Seems that these latest flavors of Windows have a little
service running known as "DNS caching". It's supposed to lock onto a
DNS server (dynamically assigned, in AT&T's case) and use that server
for the next 300 seconds (the default setting - hackable in the
registry). The idea is, if your machine doesn't have to sense which
DNS server is being assigned to it each time you click a link, your
online experience should be marginally faster. Problem is, AT&T is
probably switching between DNS servers faster than the expected 300
seconds and this explains why I can only get to about 7 sites at a
time. If I leave it alone for a few minutes, I can grab another few
pages - or I can force this process by refreshing my connection.
 
All I had to do is go into "Services" and change DNS caching from
Automatic to Manual and stop the service. DNS is once again set to
dynamically grab whatever AT&T is throwing at me and pages are once
again flying! My speed is still nailed at about 1.5mb/sec and I have
the "piece of mind" of knowing that AT&T is at least providing the
service they're being paid to provide.
 
Win9x (Linux? Mac?) doesn't suffer from this new "feature" in 2000 or
XP. While disabling it as I have is supposed to decrease web page
flipping (since the system has to sense the DNS server each time), I
honestly haven't noticed any difference. At least I have connectivity
for all apps again!
 
Just in case you're wondering, I found mention of this little goodie
at: http://www.dslreports.com/forum/remark,1932223~root=attbi~mode=flat
 
Please forward this tidbit to anyone you know might benefit from it.

"A Schwartz" <aschwartz12@attbi.com> wrote in message news:<6BWP7.7359$ER5.259417@rwcrnsc52>...
> Your fix works for me Michael, thank you, I added DNS numbers to the TCP/IP
> setting on my XP machine.  I left the router with DHCP enabled and no DNS
> entered.  Everything works fine, but I wonder what will happen when the
> connection expires.  I ran an ipconfig/release and then an ipconfig/renew to
> test and it still works, but wondering if this is a permanent solution as I
> am not always around to reset things.  I also wonder why ATT is not
> addressing this situation and we need to gather fixes from fellow
> users/consumers.
> Thanks again for the info.
> 
> Andy