| To Anonymous Coward Let me pick a part a lot of what your saying:
1.You say Packet8 failed by entrusting register.com, but you fail to mention that a lot of major companies, such as Cox, Verizon, AT&T, Brighthouse, ect. Where they did fail is by NOT faulting over to a different DNS
2. Yes, with a domain you have a seperate DNS server, which is then redirected to each one of the Packet8 users. How can a company be prepared when their domain host changes the server name and location on them without notification? If you owned a website being hosted by a smaller domain holder, and they made the change on you, how would you cope?
3. NO ACTION REQUIRED BY ISP'S? Are you crazy? They, just like any other adverage Joe, MUST reset their DNS tables after an outage, and they did. They are quicker to the punch than packet8, because they have to be. They are an extremely large company with fault over servers, packet8 is not
4. Have you even checked your sources other than with Packet8, because register.com has released statements of appology, Verizon has notified that their customers should all be back up, although some might not be and need a dns flush. So where exactly does the smokescreen exist?
5. No, I dont expect ISP's to refresh it just for packet8, I expect them to refresh for my sake, the dsl consumers! As i said before, this is not only a fault of packet8, but of a lot of other companies as well
Finally, I dont not like packet8 anymore than the other people here, you can even say i loathe it, but there is no way that you should place the blame solely on them. There does need to be blame on them, yes, but not all of it. there is a lot of companies the "blame game" should be divided between, one being Register.com |
