Article View: comp.dcom.modems.cable
Article #656Re: New AT&T Broadband Internet DHCP problem!!
From: Warren H.
Date: Sat, 08 Dec 2001 02:24
Date: Sat, 08 Dec 2001 02:24
43 lines
3331 bytes
3331 bytes
Never anonymous Bud wrote: > Using crayons of red and green, "Warren H." <wholzem@hotmail.com> scribbled > > >ROFLO! Re-read what you just wrote. When you say "much more often than > >Windows 2000 or XP expects it", do you mean more often than once every 4 > >days? My lease is for 4 days. Are you saying that they change DNS servers > >more often than that? Then explain why it wouldn't affect other OS's? > > You're obviously confusing DNS with DHCP. > No, you're missing the point. The DNS servers are configured by DHCP. If my lease doesn't expire for 4 days, then I'm not going to get a new set of DNS servers to use for 4 days. And that's going to apply to any OS I use. So if AT&T is changing their DNS servers "much more often than Windows 2000 or XP expects it", then they would also be changing those servers more often than any other OS expects it because we're all using 4 day leases. The DNS servers are NOT changing "much more often than Windows 2000 or XP expects it". Or more often than any other OS expects it. As a matter of fact, I've had the same DNS servers since ATTBI came online last Saturday morning. Once more for those in the back rows: What DNS servers are to be used is something that is delivered in the lease you get through DHCP. Thus your DNS servers can't change until you get a new lease regardless of what OS you're using -- unless you go in there and manually set different DNS settings from what was delivered through DHCP. -- 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:
<bReQ7.14636$L51.31622@rwcrnsc54>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!howland.erols.net!news-out.worldnet.att.net.MISMATCH!wn3feed!worldnet.att.net!204.127.198.204!attbi_feed4!attbi_feed3!attbi.com!rwcrnsc54.POSTED!not-for-mailReferences:
<Xns916EE6793ADD4aphotographerhomecom@63.240.76.16> <6BWP7.7359$ER5.259417@rwcrnsc52> <1334fcc5.0112071122.26c4e5c8@posting.google.com> <vQcQ7.15019$ER5.265784@rwcrnsc52> <bfq21uoumhpja2icm71ejod5qvab56gtk2@4ax.com>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: 10f392,9036b507d9187c3d X-Google-Attributes: gid10f392,public X-Google-Thread: 113850,9036b507d9187c3d X-Google-Attributes: gid113850,public X-Google-ArrivalTime: 2001-12-07 18:24:07 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!howland.erols.net!news-out.worldnet.att.net.MISMATCH!wn3feed!worldnet.att.net!204.127.198.204!attbi_feed4!attbi_feed3!attbi.com!rwcrnsc54.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> <6BWP7.7359$ER5.259417@rwcrnsc52> <1334fcc5.0112071122.26c4e5c8@posting.google.com> <vQcQ7.15019$ER5.265784@rwcrnsc52> <bfq21uoumhpja2icm71ejod5qvab56gtk2@4ax.com> Subject: Re: New AT&T Broadband Internet DHCP problem!! Lines: 46 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: <bReQ7.14636$L51.31622@rwcrnsc54> Date: Sat, 08 Dec 2001 02:24:07 GMT NNTP-Posting-Host: 204.127.202.211 X-Complaints-To: abuse@attbi.com X-Trace: rwcrnsc54 1007778247 204.127.202.211 (Sat, 08 Dec 2001 02:24:07 GMT) NNTP-Posting-Date: Sat, 08 Dec 2001 02:24:07 GMT Organization: AT&T Broadband