Article View: comp.dcom.modems.cable
Article #644Re: New AT&T Broadband Internet DHCP problem!!
From: Warren H.
Date: Thu, 06 Dec 2001 08:17
Date: Thu, 06 Dec 2001 08:17
39 lines
2830 bytes
2830 bytes
Michael Feinberg wrote: > In at least my region, there is a problem with the DNS server settings being > provided by the DHCP server. It is responding with 4 DNS servers, but only > the first 2 are true DNS servers. The last two appear to be DHCP servers. > The first 2 DNS servers appear to be timing out on requests. This is causing > secondary, and then tertiary servers to be queried. In my case, once DNS > cycled to the third server I was toast as there was no way I could have a > chance to resolve DNS again as the OS (Windows) doesn't reset to the primary > DNS server on it's own. I think we have a winner! And the reason why those of us with both 2000/XP and 9x/ME machines are only seeing the problem on the 2000/XP machines but not the 9x/ME machines is that 9x/ME apparently will go back to the primary DNS server first each time, while 2000/XP will not reset. I changed my DNS settings in XP to only specify the first two (the real) DNS servers, and it appears to have resolved the issue. Excellent! > I did call in this to AT&T, but I dount it will get forwarded to whoever > would need to see it. Eventually they will figure it out... Well I certainly hope they will figure this out! -- Warren H. ========== Disclaimer: My views reflect those of myself, and not my employer, my friends, nor (as she often tells me) my wife. Any resemblance to the views of anybody living or dead is coincidental. No animals were hurt in the writing of this response -- unless you count my dog who desperately wants to go outside now.
Technical Details
Message-ID:
<AQFP7.2222$Yy.259449@rwcrnsc53>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn4feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc53.POSTED!not-for-mailReferences:
<Xns916EE6793ADD4aphotographerhomecom@63.240.76.16>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10298d,9036b507d9187c3d X-Google-Attributes: gid10298d,public X-Google-Thread: 113850,9036b507d9187c3d X-Google-Attributes: gid113850,public X-Google-Thread: 10f392,9036b507d9187c3d X-Google-Attributes: gid10f392,public X-Google-ArrivalTime: 2001-12-06 00:17:36 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn4feed!worldnet.att.net!204.127.198.203!attbi_feed3!attbi.com!rwcrnsc53.POSTED!not-for-mail From: "Warren H." <wholzem@hotmail.com> Newsgroups: comp.dcom.modems.cable,alt.cable-ip,cableinet.cable_modems References: <Xns916EE6793ADD4aphotographerhomecom@63.240.76.16> Subject: Re: New AT&T Broadband Internet DHCP problem!! Lines: 42 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: <AQFP7.2222$Yy.259449@rwcrnsc53> Date: Thu, 06 Dec 2001 08:17:36 GMT NNTP-Posting-Host: 204.127.202.211 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc53 1007626656 204.127.202.211 (Thu, 06 Dec 2001 08:17:36 GMT) NNTP-Posting-Date: Thu, 06 Dec 2001 08:17:36 GMT Organization: AT&T Broadband