Hello All,

Melbourne IT restored the nameservers and contact details associated
with this name first thing this morning (Monday in Melbourne,

We are arranging with the previous registrar (Dotster) to have the name
transferred back.

We are also investigating the chain of events that led to the problem in
the first place. This will take longer, due to the various timezones
and parties involved. In this case one of the parties was an ISP in the
United Kingdom, which is a reseller of Melbourne IT.

Bruce Tonkin
Chief Technology Officer
Melbourne IT

Bruce Tonkin wrote:

Hello All,

Melbourne IT restored the nameservers and contact details associated
with this name first thing this morning (Monday in Melbourne,

And the lack of response on a weekend is completely inappropriate. I'm glad you finally decided to do something, but there is no way in good conscience I can recommend MIT to anyone at this point.

This is analogous to a conversation I had with a friend this past week. He's owed me money for quite some time, and FINALLY gave me part of it several months ago, but only part. When I complained, he said "but I GAVE YOU money already..."

Of course he did, but his resolution of the problem took a long time and wasn't a complete resolution.

Similarly, your resolution of the problem took way too long to get started. I suspect there are PANIX customers who have suffered real losses as a result of this problem, much like the ISP I used to work for suffered when some idiot working for Network Solutions fat-fingered a domain change and took the ISP's main domain name off the net for three days (this was back in the late 90s). Your response is better than that of the NetSol moron I talked to who seemed to think the incident was funny, but there is no excuse for you not AT LEAST having a 24-hour emergency pager/cell phone/OOB notification system for incidents like this. MIT is a registrar. You knew about the change in ICANN policy and should have been proactive in setting up a safety net for people who ended up getting caught by it.

I'm not blaming you for the problem itself - I'm blaming you for not acting immediately when notified of it, and apparently adopting a "so what?" attitude on top of that. Not very professional.

I can think of at least two big registrars that have 24x7 customer service. I'm not even asking for that much from you...

I find it interesting that you assert that the ISP/reseller was in the
United Kingdom. Our investigations established that the ISP appeared
to be in Ottawa, Canada: with various whois entries which, if believed,
would have placed them in Wilmington, Delaware, and/or Beckenham, Kent
and/or what looks like a mail forwarding service on the Isle of Man
(which is NOT part of the UK ...)

Where Registrars deal extensively through resellers, it is equally
important for those resellers to be as accessible and accountable as
the Registrar - and much of the difficulty in this case was caused by
the inability to identify exactly who and where the reseller was.

Not that the problem is in any way new - we encountered difficulties
(as an ISP) in contacting this same reseller, when trying to transfer
a domain for one of our clients, many months ago, and at the time
I wrote to your Melissa Fitzpatrick to convey my concern about the
non-contactability of the reseller - and also about the questionable
whois entries.

There was, of course, no meaningful reply, and I believe that if your
company had addressed this at the time in a more professional manner,
it is highly likely that most of the problems that were experienced
this past weekend could have been avoided.