Recently I’ve experienced much downtime with my ISP, Comcast. I was able to narrow it down to their DNS servers, because their gateway was reachable. The DNS servers, on the other hand, were completely off the map. All ping requests timed out. After fiddling with router settings and renewing our IP address, I got the DHCP server to assign me new DNS servers which are working (at least for now).

This isn’t the first time this has happened. Over the past few weeks, I’ve experienced this problem several times. Last week my dad called Comcast and found that they were aware of this problem and that they were “working on it.”

When the servers went down again today, I just had to find out what was really going on. I googled for “comcast dns outage”–the situation was just as I had suspected. Why Comcast is chasing DNS outages | Between the Lines | ZDNet.com reveals that Comcast’s DNS architecture just isn’t enough to handle DDoS attacks.

Because they’ve got no management tools and little or no failover, when they get hit, they can’t respond effectively. They’re essentially fighting a five alarm fire with a bucket brigade. As a consequence, they have had multiple, multi-million customer, multi-hour outages.

Hopefully they’ll get this problem fixed soon, because you really can’t do that much on the computer without Internet access. :-D

Why Comcast is chasing DNS outages by ZDNet‘s Phil Windley — If you’re not a Comcast customer, you’re probably blissfully unaware of the problems that Comcast customers have been experiencing the last few weeks. If you are a Comcast customer, then like me, you’ve likely experienced serious downtime and you’re probably wondering what’s going on. I’ve heard a few things through the grapevine and what I’ve [...]

Newbies to web publishing often mess up their sites. They make their content inaccessible due to their wacky layouts, distracting animations and JavaScript, and excessive slang.

This is ESPECIALLY true of the cut ‘n paste code users on Xanga. Lots of tech-savvy people despise Xanga. Some say it’s because of its closed-source, proprietary nature, but I don’t really agree. Xanga itself is okay, but it’s the individual people using Xanga that give it a bad reputation.

When people think they’re making their site layouts kewl, they also cause it to become counterintuitive and counterproductive.

Here’s the list of generally disliked practices for any site–not just Xanga. It’s in order of severity, starting with the worst offense.

1. Text that is (virtually) the same color as the background. Also known as “spoiler text”. If you have to highlight text to read it properly, the user will be very annoyed. Highlighted text also often disrupts embedded images, inverting colors or dithering a dim color in. Also, it makes possibly nice layouts look disgusting because the words are “boxy” and every element on the page is highlighted. Why force your users to CTRL-A/APPLE-A, or worse, triple-click, just so they can read your page?
2. 31337 $P33k, rAnDOm cApS, ALL CAPS, no caps, and rely hard2read chatr slang. C4n U 34$!1y r34d th1$? (Can you easily read this?) hOw bOuT ThIs, iS tHiS cOOl oR wHAt?! Capitalization was designed to help letters to naturally flow together, but rANdoM cAPs breaks up this flow, AND ALL CAPS CAUSES WORDS TO APPEAR IN BLOCKS WHICH ARE HARD TO READ. no caps n hrd2rd slang + carless mispelings will cause most visitors to head for that green left-pointing arrow on their browser.
Continue reading →