Chuck, >More on the MS/DNS problem (IF that is what it was...)... I find it interesting that MS is placing the blame on their own technicians messing up the DNS entries. Yesterday Matt Drudge posted the (alledged) results of a whois which would seem to implicate more than just employee error. By the time I read it and did my own whois, MS was back up and working. And although Drudge has removed the link from his main page, the report can still be viewed at http://www.drudgereport.com/msft.htm The first few entries returned by the whois were quoted as: MICROSOFT.COM.SHOULD.GIVE.UP.BECAUSE.LINUXISGOD.COM MICROSOFT.COM.SE.FAIT.HAX0RIZER.PAR.TOUT.LE.ZOY.ORG MICROSOFT.COM.OWNED.BY.MAT.HACKSWARE.COM MICROSOFT.COM.N-AIME.BILL.QUE.QUAND.IL.N-EST.PAS.NU MICROSOFT.COM.MUST.STOP.TAKEDRUGS.ORG MICROSOFT.COM.IS.SOON.GOING.TO.THE.DEATHCORPORATION.COM (etc) If this was due to employee technician error, I'll bet they'll be out of a job soon. :) Doug +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.