Friday, April 08, 2005
What a night last night was. The DNS servers went down. Of course, we may have lost some customers last night. The thing I can't figure out is why the DNS server went down for six hours. It was a nation wide event and caused the phones to back up 60 callers deep. Of course, they put a message on the phones that everyone had to listen to a message that said that all of the internet customers were down.
Of course, that didn't stop stupid questions such as, "I heard on the recorded message that all of middle Tennessee is down, but does that include Antioch?" or "Do you know when it will be back up?"
Of course, had I thought about it, I could have gotten a lot of people up and running temporarily. After all, it's just a DNS server down. After work, I went to a favorite site.
Here's what happened. If you type in a website address, your internet service provider stores IP addresses for that website's server. Therefore when the DNS server went down, Comcast had no idea where the website that you requested was located. If I had thought about it, I could have just found a DNS for the folks to use temporarily.
Of course, I guess I was just to busy getting yelled at to think about that. That explains why people's AIM, MSN messenger, and Weatherbug were still working. Those things have either assigned IP addresses, are using a different DNS, or just remembered what it was from yesterday.
Some times I just feel silly. I should have known how to fix it. Of course, since Comcast customers "obtain a DNS server automatically", Comcast could have just changed one server for another. Surely they could have managed to do that in less than six hours.
Of course, that didn't stop stupid questions such as, "I heard on the recorded message that all of middle Tennessee is down, but does that include Antioch?" or "Do you know when it will be back up?"
Of course, had I thought about it, I could have gotten a lot of people up and running temporarily. After all, it's just a DNS server down. After work, I went to a favorite site.
Here's what happened. If you type in a website address, your internet service provider stores IP addresses for that website's server. Therefore when the DNS server went down, Comcast had no idea where the website that you requested was located. If I had thought about it, I could have just found a DNS for the folks to use temporarily.
Of course, I guess I was just to busy getting yelled at to think about that. That explains why people's AIM, MSN messenger, and Weatherbug were still working. Those things have either assigned IP addresses, are using a different DNS, or just remembered what it was from yesterday.
Some times I just feel silly. I should have known how to fix it. Of course, since Comcast customers "obtain a DNS server automatically", Comcast could have just changed one server for another. Surely they could have managed to do that in less than six hours.
Comments:
Post a Comment
