There's something funky going on. I wonder if any other ATT@Home subscribers are seeing it.
AT&T mailed out both e-mail and snail mail stating that to get updates on this situation we should go to http://help.broadband.att.com.
When I try to get to that page normally I get nothing. No page. When I do a ping to that address it resolves (via Excite's DNS controllers) to 209.19.5.9 (further identified as gilera.tci.net).
I eventually got to the page via a few round-about methods other users aren't likely to use. The actual address for the page, given by AT&T off their main site, is http://198.178.8.101.
Now, maybe it's just a bad entry in @Home's DNS controller, but isn't it funny how the page that most ATT@Home users are going to want to get to at this time is being misdirected? Especially since the same DNS controller correctly resolves broadband.att.com as 198.178.8.166?
Deliberate sabotage or just gross negligence on the part of their network admin?
I don't know how this might be working in other parts of the country. It could be a locally assigned DNS controller, but @Home doesn't want to give you a choice in the matter of what controllers you use. They are assigned via DHCP, or are supposed to be.
Slashdot Mirror
Actually, the judge decreed 3:00 a.m. Eastern as the witching hour when @Home is allowed to cut the juice.
There's something funky going on. I wonder if any other ATT@Home subscribers are seeing it. AT&T mailed out both e-mail and snail mail stating that to get updates on this situation we should go to http://help.broadband.att.com. When I try to get to that page normally I get nothing. No page. When I do a ping to that address it resolves (via Excite's DNS controllers) to 209.19.5.9 (further identified as gilera.tci.net). I eventually got to the page via a few round-about methods other users aren't likely to use. The actual address for the page, given by AT&T off their main site, is http://198.178.8.101. Now, maybe it's just a bad entry in @Home's DNS controller, but isn't it funny how the page that most ATT@Home users are going to want to get to at this time is being misdirected? Especially since the same DNS controller correctly resolves broadband.att.com as 198.178.8.166? Deliberate sabotage or just gross negligence on the part of their network admin? I don't know how this might be working in other parts of the country. It could be a locally assigned DNS controller, but @Home doesn't want to give you a choice in the matter of what controllers you use. They are assigned via DHCP, or are supposed to be.