Another tweet update from @ComcastCares: *I am on the bridge with a lot of egineers and vendors trying to resolve the DNS outage as quickly as possible.* *I apologize for the down time* -- *Colleen Velo email: cmvelo@gmail.com* On Sun, Dec 5, 2010 at 8:15 PM, Kevin Blackham <blackham@gmail.com> wrote:
I got some new entries this week:
nameserver 75.75.75.75 nameserver 75.75.76.76 domain hsd1.ut.comcast.net. search hsd1.ut.comcast.net.
Rushed out some anycasted fu after Cox's epic failure?
On Dec 5, 2010, at 19:02, Matthew Dodd <mdodd@doddserver.com> wrote:
Interesting. No issues showing from the Comcast.net DNS page. I also don't see either of those IP addresses listed there.
http://dns.comcast.net/status.php
-Matt
On Dec 5, 2010, at 8:52 PM, Michael Butler wrote:
On 12/05/10 20:32, Jared Mauch wrote:
Anyone else having issues with the comcast resolvers?
68.87.77.130 68.87.72.130 are the two I am concerned about...
While they're reachable on comcast's network from Boston, neither (WI or IL servers) appear to be answering DNS requests,
imb _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages