```json
{
    "title": "Comcast DNS Outages More Severe than Previously Thought",
    "url": "https://performancezen.com/2005/04/14/comcast-dns-outages-more-severe-than-previously-thought/",
    "datePublished": "2005-04-14",
    "dateModified": "2005-04-14",
    "language": "en-US",
    "description": "Now, I never even heard about this Comcast outage until this morning. [here] One reason that I likely didn't notice it is that I run my own caching name servers…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Comcast DNS Outages More Severe than Previously Thought

Now, I never even heard about this Comcast outage until this morning. [[here](http://news.com.com/Another+broadband+outage+strikes+Comcast/2100-1034_3-5669961.html)]
One reason that I likely didn't notice it is that I run my own caching name servers on my home network. I do this because I have never trusted any provider's overworked name servers (goes back to the history of the industry I work in; more on that some other time).
This is still a fairly crippling outage. Surely there is some redundancy in the Comcast name server infrastructure...please?
There is a list of possible workarounds to this problem linked from [here](http://www.makeyougohmm.com/20050414/1712/).
