Now to cover the issue of the "fake" controversy associated with Norm's website. Norm's website was not intentionally taken down by anybody within the campaign. The site is run from a remote location. I have logically concluded that his site crashed for one of two reasons, (i) either an extreme amount of traffic, or (ii) poor coding resulting in a memory leak. If the site was getting hit with a decent amount of traffic, which does appear to be the case, the number of database connections may have exceeded the allowable limit due to poor coding. When this happens there is essentially nothing that can be done from a remote location. The server is inaccessible because the processor is always trying to catch up with the current number of requests. In order to fix the problem, the admin would need access to the server, but they could not gain access because the server was constantly busy. Their solution was to redirect traffic to the IP address 1.1.1.1. They would have been wise to setup of an error page on another server and redirect to that, but I don't know the details.

Whenever the IP address is changed, the new address must propagate back through the internet; this can take up to 72 hours. To compensate for this delay, they changed the TTL to 600 for the 1.1.1.1 IP address, which is a very small amount of time in this application. They wanted the dummy address to propagate to as many people as possible as fast as possible so that they could attempt to fix the original error. In changing the TTL they are able to gain access to the original server faster, without the new address propagating through the internet over the actual server address. In changing the address they made a calculated decision; one I would guess they currently regret.

When their old server came back online, each and every file they had hosted was available for download. There were documents available that would not have justified any publicity stunt. My guess is that somebody outside of the campaign initially discovered the outage and began to push the "excessive traffic from voter database leads to crash" story. At this point the story was picked up by drudge.com and the Coleman was really left with really no choice but to propel the story. If they had actually acknowledged the problem, the news would have spread faster than they could have fixed; which happened anyway, but it took some time for people to figure out that files were available. I do not believe the initial crash was intentional, I believe it was a very poor implementation of technology that forced the Coleman campaign to run with the spin.

Source: Litigation, Day 3 via VoteForAmerica.net