9,082
edits
Changes
Jump to navigation
Jump to search
Line 95:
Line 95: − +
→Microsoft and ICANN
==Microsoft and ICANN==
==Microsoft and ICANN==
On January 24, 2001, Microsoft Benelux Support Manager Ruud de Jonge confirmed that Microsoft website that majority of Microsoft websites were down due to a problem in the system that maps Web addresses to IP (Internet Protocol) addresses. In a statement Jonge said, "It can be a system or human error, but somebody could also have done this intentionally. We don't manage the DNS ourselves, it is a system controlled by the Internet Corporation for Assigned Names and Numbers (ICANN) with worldwide replicas."<ref>[http://archives.cnn.com/2001/TECH/computing/01/24/microsoft.blackout.idg/index.html CNN Archives]</ref> This sparked comments from the internet community and some concluded that Microsoft is blaming ICANN for the failures of its domain name servers.<ref>[http://www.irbs.net/internet/nanog/0101/0729.html]</ref>
On January 24, 2001, Microsoft Benelux Support Manager Ruud de Jonge confirmed that Microsoft website that majority of Microsoft websites were down due to a problem in the system that maps Web addresses to IP (Internet Protocol) addresses. In a statement Jonge said, "It can be a system or human error, but somebody could also have done this intentionally. We don't manage the DNS ourselves, it is a system controlled by the Internet Corporation for Assigned Names and Numbers (ICANN) with worldwide replicas."<ref>[http://archives.cnn.com/2001/TECH/computing/01/24/microsoft.blackout.idg/index.html CNN Archives]</ref> This sparked comments from the internet community and some concluded that Microsoft blamed ICANN for the failures of its domain name servers.<ref>[http://www.irbs.net/internet/nanog/0101/0729.html Microsoft Blames ICANN]</ref>
After the failures were resolved, Microsoft issued and apology to its customers and explained that the operational errors were not caused by any third party instead a Microsoft technician made a wrong configuration change to the routers on the edge of Microsoft's Domain Name Server
After the failures were resolved, Microsoft issued and apology to its customers and explained that the operational errors were not caused by any third party instead a Microsoft technician made a wrong configuration change to the routers on the edge of Microsoft's Domain Name Server