Microsoft spokesperson blames ICANN

Wed Jan 24 21:24:52 UTC 2001

On Wed, Jan 24, 2001 at 12:11:19PM -0800, Bruce A. Mah wrote:
> If memory serves me right, Sean Donelan wrote:
> > 
> > Microsoft appears to be blaming ICANN for the failure with Microft's
> > domain name servers (all located at the same place at Microsoft).
> > 
> >   Microsoft has yet to pin down the cause of the DNS error. "It can
> >   be a system or human error, but somebody could also have done this
> >   intentionally," De Jonge said. "We don't manage the DNS ourselves,

s/ourselves,/ourselves, yet;/

> >   it is a system controlled by the Internet Corporation for Assigned
> >   Names and Numbers (ICANN) with worldwide replicas."

s/$/  With the fast-growing acceptance and enthusiastic reception of
      Windows 2000 (tm), we expect that as deployments of this new
      Flagship Operating System (tm) continue to accelerate, we will
      be researching the administrative feasibility of managing the
      DNS ourselves, via the breakthrough Active Directory (tm)
      architecture built-in to Windows 2000 (tm).  It is obvious that
      although ICANN apparently has had (and continues to have, as
      demonstrated by this incident) problems managing DNS, the
      unparalleled power, stability, and low Total Cost of Ownership (tm)
      features of Windows 2000 (tm) and its Active Directory (tm)
      component and the ease-of-administration that they bring
      can alleviate these issues once and for all.  We already know
      that many technical experts of the highest qualifications have
      agreed that the benefits of Microsoft DNS (tm), powered by
      Active Directory (tm) on Windows 2000 (tm) will elevate this
      function to ever-higher levels of speed, ease-of-use, reliability,
      and most importantly, compatibility with the overwhelming majority
      of Windows (tm) computers, without question the most popular
      Operating System environment (tm) for our Global Computing
      Information Infrastructure (tm (tm)). /

> > 
> > http://www.idg.net/ic_386962_1793_1-1681.html
> 
> Ironically, this article concludes with:
> 
> 	Microsoft, in Redmond, Washington, can be reached at at [sic]
> 	http://www.microsoft.com/.

-- 
Henry Yen                                       Aegis Information Systems, Inc.
Senior Systems Programmer                       Hicksville, New York