Slashdot Mirror


New York's Oldest ISP Gets Domain-Jacked

Howard Roark writes "Panix, the oldest commercial Internet provider in New York, had its domain name 'panix.com' hijacked by persons unknown. The main effect on users is that mail sent to panix's customers is being routed to a bogus mail server run by the hijackers."

90 of 447 comments (clear)

  1. Panix by UnCivil+Liberty · · Score: 5, Informative

    One domain hijacked and another soon to be slashdotted, sucks to be them.

    Just in case:
    "Status as of Sat Jan 15 22:04:33 EST 2005

    Panix's main domain name, panix.com, has been hijacked by parties unknown. The ownership of panix.com was moved to a company in Australia, the actual DNS records were moved to a company in the United Kingdom, and panix.com's mail has been redirected to yet another company in Canada. Panix staff are currently working around the clock to recover our domain, but this may take until Monday, due to the time differences and difficulties in reaching responsible parties over the weekend.

    For most customers, accesses to Panix using the panix.com domain will not work or will end up at a false site."


    Their catch phrase "Your $HOME away from home" is quite cute.

    --
    Distributed proteome folding @ WorldCommunityGrid.org
    Team Slashdot - Members:#1 Run Time:#1 Points:#1 Results:#1
    1. Re:Panix by wpanderson · · Score: 4, Informative

      Looks like their MX records are back under their own control ...

      intrepid:~> dnstracer -s . panix.com
      Tracing to panix.com[a] via A.ROOT-SERVERS.NET, maximum of 3 retries
      A.ROOT-SERVERS.NET [.] (198.41.0.4)
      |\___ M.GTLD-SERVERS.NET [com] (192.55.83.30)
      | |\___ ns2.ukdnsservers.co.uk [panix.com] (207.61.90.196) Got authoritative answer
      | \___ ns1.ukdnsservers.co.uk [panix.com] (142.46.200.67) Got authoritative answer
      [snip]
      intrepid:~> host -t mx panix.com
      panix.com MX 200 mailhost-l2.panix.com
      panix.com MX 150 mailhost.panix.com
      intrepid:~> host -t any mailhost.panix.com
      mailhost.panix.com does not exist, try again
      intrepid:~> host -t any mailhost-l2.panix.com
      mailhost-l2.panix.com A 166.84.1.75
      intrepid:~> whois 166.84.1.75

      OrgName: Panix Public Access Internet
      OrgID: PPAI
      Address: 15 West 18th St.
      Address: 5th Floor
      City: New York
      StateProv: NY
      PostalCode: 10011
      Country: US

      NetRange: 166.84.0.0 - 166.84.255.255
      CIDR: 166.84.0.0/16
      NetName: ACCESS-NET-B
      NetHandle: NET-166-84-0-0-1
      Parent: NET-166-0-0-0-0
      NetType: Direct Assignment
      NameServer: NS1.ACCESS.NET
      NameServer: NS2.ACCESS.NET
      Comment:
      RegDate: 1993-11-10
      Updated: 2000-08-21

      TechHandle: PANIX5-ARIN
      TechName: Panix Network Information Center
      TechPhone: +1-212-741-4400
      TechEmail: hostmaster@panix.com

      OrgTechHandle: PANIX5-ARIN
      OrgTechName: Panix Network Information Center
      OrgTechPhone: +1-212-741-4400
      OrgTechEmail: hostmaster@panix.com

      # ARIN WHOIS database, last updated 2005-01-15 19:10
      # Enter ? for additional hints on searching ARIN's WHOIS database.

      ... or did I miss something

      --
      neuro at well dot com (when I post, it's my opinions, no-one elses)
    2. Re:Panix by multipartmixed · · Score: 2, Informative

      I'm still getting the freeparking IP for the MX from my local servers, but network-tools.com is showing the right info.

      Presumably my stuff is cached; but at least the TTL on the hijacked domain is to 7200s. Nice and short.

      --

      Do daemons dream of electric sleep()?
    3. Re:Panix by canuck57 · · Score: 2, Insightful

      but this may take until Monday, due to the time differences and difficulties in reaching responsible parties over the weekend.

      I smell a law suit a happening. But given the lack of response from this registrar their registration should be pulled if they don't have it fixed with 30 minutes notice.

      And maybe ISPs will lean on ICANN to remove the registrar. It is easy to protest. If the top ten ISPs blocked this registrars DNS servers this would in fact make it worth their while to get their act together. If I worked for Earthlink, RR, Sprint, Simpatico, Telus, ATT and others, and had the authority to do this I would participate. As there has to be NO DNS registrar that is fradulent. As it could have been my domain that was hyjacked.

    4. Re:Panix by rs79 · · Score: 4, Interesting

      It's not like you folks wern't warned this would happen. The NSI-ICANN agreement took away any power NSI had to fix this.

      An in band solution altering DNS is probably not a solution, welcome to the modern internet and oddly, I don't see a peep out of ICANNs "Transfer Task Force".

      The proper geek way to fix this is with BGP. Why hasn't anybody had the cajones to do this yet?

      If somebody cares to contact me preferably by voice I can put the correct NS records for panix i the ORSC root zone and those of you sensible enough to not rely on other people to be in charge of the entire domain tree will be able to get to (alas) poor Panix normally.

      John Berryhill is in Deleware and is now aware of the problem. When he stopped laughing he said he'd make some calls, lawyer to lawyer. And he is in Deleware. The address in DE of the NS host to panix is a residence, FWIW. Wilmington is not a large place...

      I must say when I heard panix had been hijacked by something in Wilmington De and Canada my heart stopped till I found out is wasn't me and John.

      If you're not scared enough, JB suggests you go to any_domain.1bu.com and welcome to the Chinese global phishing site.

      --
      Need Mercedes parts ?
    5. Re:Panix by Simon+Brooke · · Score: 4, Informative

      As of 17:03 GMT, I am getting (via British Telecom's nameservers):

      Domain Name.......... panix.com
      Creation Date........ 1991-04-22
      Registration Date.... 2005-01-15
      Expiry Date.......... 2006-04-23
      Organisation Name.... vanessa Miranda
      Organisation Address. 1010 Grand Cerritos Ave
      Organisation Address.
      Organisation Address. Las Vegas
      Organisation Address. 89123
      Organisation Address. NV
      Organisation Address. UNITED STATES

      Admin Name........... na vanessa Miranda
      Admin Address........ 1010 Grand Cerritos Ave
      Admin Address........
      Admin Address........ Las Vegas
      Admin Address........ 89123
      Admin Address........ NV
      Admin Address........ UNITED STATES
      Admin Email.......... jzoh@yahoo.com
      Admin Phone.......... +44.702413697
      Admin Fax............ +44.7026413697

      Tech Name............ Domain Admin
      Tech Address......... Burnhill Business Centre
      Tech Address.........
      Tech Address......... Beckenham
      Tech Address......... BR3 3LA
      Tech Address......... Kent
      Tech Address......... GREAT BRITAIN (UK)
      Tech Email........... admin@powerhost.co.uk
      Tech Phone........... +44.2082496081
      Tech Fax............. +44.2082496076
      Name Server.......... ns1.ukdnsservers.co.uk
      Name Server.......... ns2.ukdnsservers.co.uk

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    6. Re:Panix by Antique+Geekmeister · · Score: 2, Interesting

      Because BGP is a technical solution to a human problem, that of verifying users requests. And the BGP traffic is already a signifant amount of traffic to core routers: adding another layer of manipulation and complexity to them is asking for more brokenness, and many of the top-tier providers manipulate their BGP information to raise the "distance" of what are fiscally expensive routes, or to blackhole people they don't like.

      Take a look at the routing wars surrounding the various spam blackhole lists if you're curious about this.

  2. Total Hypocrisy, Michael by Jewcatur · · Score: 5, Informative
    Wow, total irony here

    Do you realize how hypocritical that Michael is posting this story when Michael himself hijacked censorware.org from the people it belonged to? I reproduce the story here (you can read the original here:

    h2>Michael Sims, Domain Hijacking and Moral Equivalency by Jonathan Wallace jw@bway.net

    How would you feel if your webmaster maliciously took your web-site offline, then, when you demanded its return, put up a site attacking your company at your old URL? It happened to a group I was involved in, the Censorware Project, currently at http://www.censorware.net. The purpose of this essay is to put the behavior on record, and to give you some impressions and inferences about it.

    The Censorware Project was originally an informal collective of six people who collaborated online to fight censorware: Seth Finkelstein, Bennett Haselton, Jamie McCarthy, Mike Sims, Jim Tyre and myself. Several of us had never met or even spoken on the phone, yet for some time -- around two years as I recall -- we had a remarkably easy collaboration. There was no funding, no hierarchy, no titles, not even project managers. Someone would suggest a project and take the responsibility for a part of it, others would sign up for other elements, and proceeding this way we got a remarkable amount of work done, including reports on X-Stop, Cyberpatrol, Bess and other censorware products.

    Even though two of us were attorneys -- Jim and myself -- we never incorporated the group or wrote a charter or any contracts among ourselves. Mike Sims was obliging enough to register the domain, just as other members paid for press releases and the other incidental expenses which came along. Mike also served as webmaster of the censorware.org site and did substantial work for the group, including writing contributions to several of the reports and lead authorship of at least one. Seth was the source of our decrypted censorware blacklists and managed many technical tasks, but later felt he had to leave the group because of the increasing prospects of a lawsuit, particularly under the Digital Millennium Copyright Act (DMCA). After Seth left the group, the remaining five continued.

    Robert Frost said that "nothing gold can stay," and the Censorware Project was no exception. Over the summer of 2000, Mike Sims' reaction to a perceived slight from Jim Tyre was to take the site down for a week. He sent us mail at the time saying something like "The Censorware Project is now closed." I replied to him that, given that the group was a collective and we all had an interest in its work product, the domain, and the goodwill it had achieved, the decision was not his to make. Sims did not reply.

    After Seth created a partial, text, mirror, Mike put the site back up a week later without explaining, let alone apologizing for, his actions. Given his continuing failure to answer any email from me (and I think from others) and the overall signs that Sims thought the group was exclusively his, I wrote him several emails requesting that he turn the domain over to Jamie or Bennett, as I felt we could no longer trust him to administer it. We also found out during that time that important email from people trying to contact us, including members of the press, was not being answered by Sims, nor being forwarded to other members.

    I ultimately became exasperated that my name was listed as a principal on what had now become a "rogue" site I had no control over. Over about

    1. Re:Total Hypocrisy, Michael by Anonymous Coward · · Score: 4, Insightful

      > Mike Sims was obliging enough to register the domain

      In other words he owned the name from the beginning, hence could not 'hijack it'.

      I'm going for a drive in my car. Can my neighbour report the car stolen? well sure, if they're stupid.

      That's what this is.

    2. Re:Total Hypocrisy, Michael by barc0001 · · Score: 2, Interesting

      Oh, I see. So because someone does something that's wrong, they can never talk about it, or post stories if someone else does the same wrong thing? Cool! I bet every cop whose ever given me a speeding ticket has sped at least once, so I can ignore them from this point on!

      So, you're one of the persons Micheal screwed over. What does that have to do with Panix?

    3. Re:Total Hypocrisy, Michael by Black+Is+Beautiful · · Score: 4, Insightful

      Note that he never said that Michael shouldn't post such things. But one must remember that a person should practice what they preach, lest they become a hypocrite.

      If michael doesn't want to be scrutinized over such things, then he shouldn't hijack domains.

      --
      www.gnaa.us
    4. Re:Total Hypocrisy, Michael by martinoforum · · Score: 5, Insightful

      It's certainly ironic, I must say. But judging by most of my reading, the sole requirement of being an editor on a Linux or Open Source related news site is to be as insufferable an asshole as possible and refuse to resign, ever, regardless.

      If it wasn't for the fact that I read Slashdot purely to be reminded of the fact that being a geek does not make you smart - something I feel it is good to remind oneself of on a regular basis - I would probably have stopped reading in horror.

      But really, it would only matter if Michael had a good job. "He hijacked their domain! And now he's a success!" they cry. A success? Jesus, by what standards!? He reads hoax stories about fish washed up by tsunamis, doesn't bother to check any facts and just posts them regardless. And that doesn't even constitute doing a bad job, by Slashdot standards. So if that's the standards they require, I can't imagine it is too hard to get qualified "journalists" to work for them, and they doubtless pay a rate commensurate to his boundless skills.

      Just get back to your Neal Stephenson books and consider him Andrew Loeb, everybody. He'll doubtless get shot in the end anyway...

    5. Re:Total Hypocrisy, Michael by Anonymous Coward · · Score: 5, Insightful

      Mike Sims was obliging enough to register the domain

      Because you didn't have any formal orginazation, he screwed you.

      That's the problem with relying on donated resources, thay can go away at any time. Mike donated the domain name and webserver, then chose not to.

      What he did next shows that he's not an honorable person, but then we knew that from his editorializing here on /..

    6. Re:Total Hypocrisy, Michael by sexysciencegirl · · Score: 5, Interesting

      Parent's post is at +5 at 12:30amPST, 1/16/05. Who wants to bet that it
      1) will be fixed at -1
      2) becomes another post of death
      before the day is over?
      It wouldn't be the first time when slashdot editors' actions go directly against their high-horse stance against censorship and try to hide any views that they personally don't like.
      I would like to remind Michael that you only support free speech if you support your enemies' rights to say things that you don't like and hope that you prove me wrong.

    7. Re:Total Hypocrisy, Michael by barc0001 · · Score: 2, Insightful

      Yes. Should pedophiles be allowed to work with children? Should a rapist be allowed to work in a women's shelter?

      Of course not. But your analogy is very flawed, because that's not what Micheal is doing here. Let me fix it for you:

      Should a rapist be allowed to call the cops on another? Should a pedophile be able to blow the whistle on another pedophile cruising the schoolyard?

      What do YOU think the answer to those two questions should be?

      Now, if this was a story about how Michael was registering another domain for another website he'd offered to "help", then your analogy would hold.
      And if you are truly not involved with that project, might I suggest you take that chip off your shoulder? Maybe Micheal isn't the nicest guy, who knows? Maybe he had a reason to do what he did, maybe not. All I read in that essay is one person's version of the facts, and as is usually the case, it's all a screed of "We did nothing wrong, he went nuts". Such things are rarely black and white, I am sure there is a lot more to the story than one person's writeup.

    8. Re:Total Hypocrisy, Michael by barc0001 · · Score: 4, Funny

      Yeah, well I got in a pissing match with an AC troll. Guess I get what I deserve.

      Way to not get it, guy.

    9. Re:Total Hypocrisy, Michael by gaspyy · · Score: 4, Interesting

      As always, misleading analogy.

      It's more like this
      Gullible Buyer: "Hey friend, you are more knowledgeable with cars, will you buy me one? Here's the cash, go to the local deader, buy whatever seems good; I don't know all the tech-speak and I am sure the sales rep. will try to rip me off"
      Friend: "Sure. Count on me" ...
      Later:
      Friend: "I bought this great car, but I made the papers on my name. But don't worry, I'll let you drive it"
      Gullible Buyer: "Uhhh, thanks, I guess" ...
      Later:
      Friend: "You know, this car is mine, so fuck off!"

      Believe it or not, I've seen this happening more than once with regard to domain names. One example: The client is a newcomer and the contractor was SO helpful, they provided the internet connection, made and hosted the company website and even registered the domain name (on their name, not the client's name). The client doesn't even notice. A few years after that, the client realizes the mistake, tries to take ownership of the domain. The contractor asks for $50,000.

      Luckily, in that case the client also has a trademark on the name, so i advised them to threaten the contractor with a lawsuit and never give in. I don't know the latest status in this matter but I think the contractor will give the domain to the rightful owner.

  3. This happens quite a bit... by eviljim · · Score: 5, Informative

    It's not surprising this has happened. Many, many companies do not take administrating their domain seriously, and several registrars -- Network Solutions especially -- make it very easy to steal domains.

    I know this from experience -- many years back one morning I woke up and Excite.com, Angelfire.com, and a few other domains were mysterically owned by me. The only thing the hijacker needed to do (it wasn't me, by the way) was send in a single email. Old Story at Wired.

    1. Re:This happens quite a bit... by John+Seminal · · Score: 3, Interesting
      It's not surprising this has happened. Many, many companies do not take administrating their domain seriously

      How do you administer domain security??? All I can think of is a tough password for the registrar. Or do all the changes by telephone only.

      --

      Rosco: "If brains were gunpowder, Enos couldn't blow his nose."

    2. Re:This happens quite a bit... by eviljim · · Score: 2, Informative

      First and foremost, choose a registrar that is secure. Under the old Network Solutions regime things were mostly done with email forms and the base method of security was verifying the "From" address an email was sent by. Yeah. That's not very secure, yet Exite was using it as opposed to at least the slightly better password or crypt-password options.

      Most registrars now use password protection and a web interface (Network Solutions does this now too). Yet like with everything else people will have stupid passwords, and some registrars allow people to have stupid passwords.

      Also, domains can be locked. This gives some security -- it prevents a transfer from going through unless you login to your current registrar to unlock the domain first. This is a bit of added security.

      Finally, make sure your email is secure and VALID. The number of people with invalid emails in their domain profile is staggering. Without a valid email you won't be notified that a domain is attempting to be transfered. If someone gets into your email, it's also likely they can get the login details for your registrar account.

      Okay that finally wasn't too final -- here's a few more things: don't deal with resellers. Go straight to a registrar and make sure they are ICANN accredited (not selling for someone else who is). Deal with a company with a good reputation.

    3. Re:This happens quite a bit... by ErichTheWebGuy · · Score: 2, Insightful

      Well, with a name like eviljim, I'm not surprised they wound up under your control [grin]

      --
      bash: rtfm: command not found
    4. Re:This happens quite a bit... by eviljim · · Score: 3, Interesting

      It can actually make a big difference... not so much for transfering (although it is possible that the reseller steal your domain), it's just another layer where something could go wrong.

      Also, resellers often have the same power you have over a domain -- they could easily change the admin contact to themselves, for example.

      Or, in a recent example, the employee of one reseller decided to delete everyone's domains. The users were forced to either pay some price over $100 to get the domain from redemption or potentially lose the domain (aside from the fact that what they paid for the domain was gone). If you care to read about that, here is a rather long thread on it.

    5. Re:This happens quite a bit... by Antique+Geekmeister · · Score: 2, Informative

      The surprise isn't that such a theft happened. The surprise is that it took this long. Verisign's willingness and ability to verify their customers' identity has been a joke for years, as thousands of throwaway domains registered by spammers and other frauds have demonstrated.

      Verisign doesn't want to verify and fully identify their customers. It's a lot of work, it doesn't create extra business, and it would make the fraud domains too traceable and cost them a significant revenue source, and would make them accountable for damages when their lax policies allow such thefts. The benefit would be to legitimate customers such as panix.com, but Verisign has always been about generating new profit sources, not improving the security of current services.

      On top of Verisign's hijacking of all unassigned *.com addresses, this is another reason for ICANN to review Verisign's ownership of the .com top level servers and consider giving them to another, more reliable provider.

  4. More details, please... by EvilStein · · Score: 4, Interesting

    *How did this happen?
    *Was it the registrar that was at fault?
    *Did they forget to renew the domain?
    *What is the registrar doing about the issue? (if anything)

    I'm kind of curious about this..

    1. Re:More details, please... by Gendalia · · Score: 5, Informative

      Panix's registrar has no record of the transfer request. Dotster's whois shows that the domain needs to be renewed by April.
      Registrant:
      Public Access Networks Corp.
      15 West 18th Street, 5th floor
      New York, NY 10011
      US

      Registrar: DOTSTER
      Domain Name: PANIX.COM
      Created on: 22-APR-91
      Expires on: 23-APR-05
      Last Updated on: 15-JAN-05

      Administrative, Technical Contact:
      Hostmaster, Panix hostmaster@panix.com
      Public Access Networks Corp.
      15 West 18th Street, 5th floor
      New York, NY 10011
      US
      212-741-4400
      212-741-5311

      Domain servers in listed order:
      NS1.ACCESS.NET
      NS2.ACCESS.NET

      End of Whois Information

  5. How can this happen?? by John+Seminal · · Score: 2, Interesting
    I am writing this as a webmaster of a smaller personal website.

    How can someone take my domain, that I paid for, and hijack it? And if you register for a domain, for a period of time, say 1 year, can someone at the end of that time come and take the domain away, or do you always get the first chance to renew?

    Does security of domains have anything to do with the company that registers??

    There are so many questions...

    --

    Rosco: "If brains were gunpowder, Enos couldn't blow his nose."

    1. Re:How can this happen?? by PornMaster · · Score: 4, Informative

      Well, first thing to do is use the feature "REGISTRAR-LOCK" to make sure that for a domain transfer, not only does there need to be authorization from the listed contacts, but also you need to log in to your registrar and unlock it first.

    2. Re:How can this happen?? by rwyoder · · Score: 2, Informative

      Well, first thing to do is use the feature "REGISTRAR-LOCK" to make sure that for a domain transfer, not only does there need to be authorization from the listed contacts, but also you need to log in to your registrar and unlock it first.

      I am following the NANOG mailing list, and the domains were locked.
  6. Re:whois by Anonymous Coward · · Score: 2, Insightful

    Ah yes, Only on Slashdot will you hear the same people bemoan their inbox being filled with spam but at the same time suggesting that spamming is a legitimate way of getting back at people you don't like.

    Have you ever thought that the email addresses listed could be of innocent people that the person responsible wants to get in trouble?

    No, of course you didn't.

  7. PROFIT by killa62 · · Score: 2, Funny

    1 steal domain 2 sell it back 3 ??? 4 PROFIT!!!

  8. Rogue registrars? by tjls · · Score: 5, Informative
    I tried to post about this about 10 hours ago, but no luck. Sigh.

    What seems to have happened is that somehow the Australian registrar "melbourneIT.com" yanked the fully paid-up registration away from Dotster (where Panix had it) without any notice whatsoever (this violates all the relevant RFCs for the Shared Registration System and the current ICANN policy *and* seems to indicate a severe bug or security problem somewhere in the registration system).

    What's particularly scary is that melbourneIT.com isn't open on the weekends, period (though oddly enough they transferred the domain first thing on Saturday, hmmmm) and won't do anything to help. There are lots of ugly details in the NANOG mailing-list archive, particularly in this message from Perry Metzger, this message from Richard Cox, and this message from me, which includes a slimy note from some customer-service flack at Verisign.

    This has clearly happened to others in the past, and highlights a serious flaw in the current registry-registrar system. We are not 100% sure how the domain was transferred between registrars with no notice to anyone (though I have some hunches I won't go into here right now) but consider this: a rogue or penetrated registrar can effectively put you out of business for the duration of the ICANN complaint and appeals process, with no notice, and there may be nothing you or anyone else can do about it short of extremely expensive legal action, even if you get law enforcement involved. Yuck.

    1. Re:Rogue registrars? by ErichTheWebGuy · · Score: 4, Interesting

      What's particularly scary is that melbourneIT.com isn't open on the weekends, period ... and won't do anything to help.

      I can vouch for this. Melbourne IT is a horrible company to try to deal with. Many US registrars (including Yahoo! domains) are resellers of Melbourne IT's services. Now, if you have a problem with your domain, just try to get in touch with someone at Yahoo. The reply I got from Yahoo was: "there is no support from Yahoo for domain names purchased through Yahoo! domains."

      Then, try to get in touch with someone at Melbourne IT. "I'm sorry, only the reseller can help you with this problem, yes even though they refuse to help you, I can't help you."

      It took me two weeks to get a domain transferred out of Yahoo/Melbourne's control and into a sane registrar that gives a crap about their customers (register.com, you can actually talk to someone on the phone there, 24/7/365).

      Seems to me that they are snappy when it comes to theft of domains, yet sluggish when it comes to any form of customer service. My advice: Boycott Melbourne IT and all of its resellers until they get a clue.

      --
      bash: rtfm: command not found
    2. Re:Rogue registrars? by Cramer · · Score: 3, Interesting

      Since when has register.com ever been a "sane registrar"? You do know they've been drug into court several times for fraud, predatory business practices, and yes, transfering domain registrations without authorization. Specificly, they were sending domain renewal notices (that looked almost exactly like netsol's notices) for domains that weren't their customers. And weren't expiring either.

    3. Re:Rogue registrars? by Aurix · · Score: 2, Insightful

      What's particularly scary is that melbourneIT.com isn't open on the weekends, period

      Perhaps you might like to check their site before you make such comments. They have 24/7 support.
    4. Re:Rogue registrars? by Anonymous Coward · · Score: 5, Informative

      I've worked for Melbourne IT, and can add a little here. I've got a little bit of info on the situation.

      It's currently about 9pm on Sunday night in Melbourne. People have been alerted. Things _are_ moving. People are most certainly aware of the situation and are working to get to the bottom of it.

      The tech contact address (admin@powerhost.co.uk) is that of one of Melb IT's UK resellers, Fibranet. Its presence would indicate the transfer was initiated under that reseller's account and their access to Melb IT's systems. Possibly (I'm speculating) someone may also have got access to the reseller's account other than the reseller.

      It wouldn't surprise me if whoever did this intentionally did this near midnight Saturday, Melbourne time, near the start of Melb IT's longest point of having the office closed (midday Saturday to 8am Monday, Melbourne time). During the week there are staff on 24 hours.

      I don't speak for Melb IT here, but I really think they're copping a lot of shit for something that's not their fault. I'm not claiming they're perfect, but hell - this was done when nobody was in the damned office. They're not _evil_ there (or perfect - just human) and would never initiate anything that'd bring down this much bad press.

      Someone's playing games and using Melb IT as a tool. It'll all get untangled before long and we'll find out who's really to blame for this.

    5. Re:Rogue registrars? by xlsior · · Score: 5, Interesting

      What seems to have happened is that somehow the Australian registrar "melbourneIT.com" yanked the fully paid-up registration away from Dotster (where Panix had it) without any notice whatsoever

      Or so they say.

      What many people here may not be aware of, is that the domain registry system had a slight overhaul recently, after ICANN mandated a change in the registrar transfer procedures.

      More specifically: while in the past a domain transfer would automatically be rejected when the account holder did not approve it, recently this changed so now a transfer request get approved by default unless the account holder actively rejects it.

      Yes -- that means that if the owner to be on vacation, doesn't check his mail frequently enough, has a spamfilter that ate the transfer notice, or simply never received the message in the first place for whatever other reason, the domain transfer request will automatically be granted.

      ICANN's reasoning for this was alledgedly that it would prevent a defunct hosting provider or non-working administrative account from keeping a customer's domain hostage.

      The only way to change this behaviour and reject a domain transfer by default, is to lock the domain with the registrar. Many of the registrars responded to this policy change by proactively locking all domains hosted with them with little warning (Network Solutions, for example)

      Anyway, it's quite likely that this domain in question simply didn't get locked (or was actively unlocked by the administrator because it was deemed inconvenient?). Then if anyone sent a (bogus) transfer request and the administrator either didn't see the notice or didn't respond in a timely fashion to reject it, this would happen.

      This will happen to ANY domain that is not currently locked, and who's admin contacts aren't paying close enough attention to their mailbox. If you haven't already done so: MAKE SURE YOUR DOMAINS ARE LOCKED!!!

      Yet another example of how ICANN makes the world a better place, I guess.

    6. Re:Rogue registrars? by Anonymous Coward · · Score: 5, Interesting
      I've been involved in investigating this for most of today. In fact, it's not just the admin and tech contacts at Panix who were never notified; the transferred-from registrar (Dotster) was never notified.


      Even under the new ICANN rules, that's not supposed to be possible. Someone is playing games with the system.

    7. Re:Rogue registrars? by tjls · · Score: 2, Informative

      No. The registrar the domain was taken from wasn't even notified of the transfer. Something is very wrong.

    8. Re:Rogue registrars? by bani · · Score: 2, Interesting

      they only shaped up when federal law enforcement forced them to. they didnt change voluntarily.

    9. Re:Rogue registrars? by Anonymous Coward · · Score: 2, Insightful

      I'm anonymous because I choose to be. Fuck - you're talking about "vigilante justice" at the drop of a hat without knowing half the facts about a situation, and you're wondering why I want to stay anonymous?

      As for your points, as has been mentioned in one or two of the more rational posts here, transfers are conducted by the top-level registry. That's Verisign, for .com domains, if you didn't know. VERISIGN.

      Under the new transfer rules, brought to us recently by the ever-lovable ICANN, transfers go ahead FIVE DAYS after they are requested unless the domain is LOCKED BY THE CURRENT REGISTRAR, or the admin contact for the domain EXPLICITLY REJECTS IT.

      Melbourne IT has no control over what's transferred in. If Verisign says "hey, you manage this domain now", even on a Sunday morning - they get it. Five days after the admin contact has failed to reject it.

      A registrar can't touch a domain until Verisign assigns control to them. They don't have special powers to magically shuffle the things around. Melbourne IT gets calls all the time from people wanting their domains transferred in with a magic transfer button, but if the current registrar has a lock on it, there's nothing that can be done.

    10. Re:Rogue registrars? by tjls · · Score: 3, Informative

      Unfortunately, you've just posted the same tired bundle of false assertions. Neither the transferred-from registrar (that's Dotster) nor Panix were actually notified prior to the transfer. In fact, if you actually read the relevant standards (in particular, the description of the TRANSFER message in RFC2832 you'd find that a change of registrar works like this: 1) The transferred-to registrar sends a TRANSFER message to VeriSign. VeriSign or the transferred-to registrar (the specification is extremely unclear) then uses an unspecified out-of-band method to contact the transferred-from registrar. 2) The transferred-from registrar sends an identical TRANSFER message to VeriSign, except that it has either Approved:yes or Approved:no in it. This is what actually causes the change to occur. 3) Since the recent ICANN change in policy, if no Approved: TRANSFER message is received in 5 days, the transfer occurs automatically. This points out some very, very odd things about this particular transfer. First, Dotster has no record of any TRANSFER request in their log file. Second, they have no record of sending any approval message -- in fact, their database still shows that Panix is their customer; they can't even try to grab the domain back without deleting the record, which would complicate the ongoing investigation. Yet VeriSign say that the domain was transferred with approval. With approval from whom, exactly? I have some strong hunches about how it might be possible to do this but I can't really go into them here and now.

  9. It's not just Censorware by bonch · · Score: 5, Interesting

    People do not like him as an editor here. Michael constantly editorializes by sticking his opinions into the article submission instead of in a comment like the rest of us have to. He often modbombs threads and blacklists people who post in them from moderating. Even if you don't like Taco's endless dupes or typos, at least he lets the submission speak for itself (iPod launch comment excluded). Michael does very unprofessional things like the infamous all-caps attack toward Intel in the 64-bit chip article last year.

    No, this is not just a hobby site where those kinds of things fly. This is a highly-visited news site, considered a major source of tech news for geeks, and a corporate-owned entity of OSTG who employs Malda and company. There's an amount of responsibility you ethically must adopt when your site gets so popular that it's name alone becomes a verb due to the server-killing power of its readerbase.

    Michael also does things like edit the words of people's submissions, like adding quotation marks around the word "revealed" in this story (now in my sig). Regardless of what you think of the story, that's just plain misleading and twisting the words and intent of the submitter, making it appear they meant something other than what they did. If it was an anonymous submitter, that would be different, but now Michael has stuffed a message into the submitter's mouth that was not there. At least show a little respect for the people who are providing your content.

    1. Re:It's not just Censorware by Doc+Ruby · · Score: 3, Funny

      I like him.

      --

      --
      make install -not war

    2. Re:It's not just Censorware by Matt+Perry · · Score: 2, Informative
      This is a highly-visited news site, considered a major source of tech news for geeks, and a corporate-owned entity of OSTG who employs Malda and company. There's an amount of responsibility you ethically must adopt when your site gets so popular that it's name alone becomes a verb due to the server-killing power of its readerbase.
      Yet how many slashdot readers have written (not emailed) OSTG to let them know how they feel? Personally, the lack of attention to checking links in stories, dupe posting, Michael's comments, etc, are what keep me from subscribing. I let them know that. Write them and let them know how you feel:
      OSTG
      46939 Bayside Parkway
      Fremont, CA 94538
      USA
      --
      Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
  10. How This Can Happen by ErichTheWebGuy · · Score: 5, Informative

    See this story on Netcraft, which details the recent policy change by ICANN.

    In short, if someone initiates a transfer request, you then have 5 calendar days to respond, or else the transfer happens unopposed. You can prevent this by activating the REGISTRAR-LOCK feature on your domain name. The procedure varies by registrar, but it's usually called "domain lock" or something similar. All registrars have to at least give you the option of requesting this feature.

    Some registrars (godaddy, I know for sure does) activate this lock by default, Some require you to activate it explicitly. Check with the support dept. at your registrar for further details.

    --
    bash: rtfm: command not found
  11. it's worse than that... by bani · · Score: 4, Informative

    ...melbourneit, the registrar responsible for the mess, basically told panix to take a flying leap. verisign wasnt any help either.

    what a sad state of affairs when it's trivial to hijack a domain, but it takes an act of god to return it to its rightful owner. apparently, even law enforcement can't get verisign or melbourneit to do squat:

    Date: Sun, 16 Jan 2005 07:04:46 +0000
    From: Thor Lancelot Simon
    To: nanog@merit.edu
    Subject: Re: panix.com hijacked (VeriSign refuses to help)

    Alexis Rosen tried to send this to NANOG earlier this evening but it
    looks like it never made it. Apologies if it's a duplicate; we're
    both reduced to reading the list via the web interface since the
    legitimate addresses for panix.com have now timed out of most folks'
    nameservers and been replaced with the hijacker's records.

    Note that we contacted VeriSign both directly and through intermediaries
    well known to their ops staff, in both cases explaining that we suspect
    a security compromise (technical or human) of the registration systems
    either at MelbourneIT or at VeriSign itself (we have reasons to suspect
    this that I won't go into here right now). We noted that after calling
    every publically available number for MelbourneIT and leaving polite
    messages, the only response we received was a rather rude brush-off from
    MelbourneIT's corporate counsel, who was evidently directed to call us
    by their CEO.

    We are also told that law enforcement separately contacted VeriSign on
    our behalf, to no avail.

    Below please find VeriSign's response to our plea for help. We're rather
    at a loss as to what to do now; MelbourneIT clearly are beyond reach,
    VeriSign won't help, and Dotster just claim they still own the domain and
    that as far as they can tell nothing's wrong. Panix may not survive this
    if the formal complaint and appeal procedure are the only way forward.

    > Date: Sun, 16 Jan 2005 00:21:33 -0500
    > To: , NOC Supervisor
    > Subject: Re: FW: [alexis@panix.com: Brief summary of panix.com hijacking incident]
    (KMM2294267V49480L0KM)
    > From: VeriSign Customer Service
    > X-Mailer: KANA Response 7.0.1.127
    >
    > Dear Alexis,
    >
    > Thank you for contacting VeriSign Customer Service.
    >
    > Unfortunately there is little that VeriSign, Inc. can do to rectify this
    > situation. If necessary, Dotster (or Melbourne) is more than welcome to
    > contact us to obtain the specific details as to when the notices were
    > sent and other historical information about the transfer itself.
    >
    > Dotster can file a Request for Enforcement if Melbourne IT contends that
    > the request was legitimate and we will review the dispute and respond
    > accordingly. Dotster can also contact Melbourne directly and if they
    > come to an agreement that the transfer was fraudulent they can file a
    > Request for Reinstatement and the domain would be reinstated to its
    > original Registrar. Dotster could submit a normal transfer request to
    > Melbourne IT for the domain name and hope that Melbourne IT agrees to
    > transfer the name back to them outside of a dispute having been filed.
    > In order to expedite processing the transfer or submitting a Request for
    > Reinstatement however Dotster will need to contact Melbourne IT
    > directly. If Dotster is unable to get in touch with anyone at Melbourne
    > IT we can assist them directly if necessary.
    >
    > Best Regards,
    >
    > Melissa Blythe
    > Customer Service
    > VeriSign, Inc.
    > www.verisign.com
    > info@verisign-grs.com

    1. Re:it's worse than that... by Aurix · · Score: 2, Informative

      As an Aussie, I don't think I'll ever deal with Melbourne IT after hearing this. Their ridiculous high prices are meant to include top support... Seems they're letting everyone down.

      Anyone know if they could stand to lose their registrar license? I mean, you can't just pass fraudulent transfers like that....

    2. Re:it's worse than that... by Fully+Sick+Like+Ot's · · Score: 3, Interesting

      Hi Aurix, You make some valid points, but the blame should definately not be put all onto Melbourne IT. I had to lock many of my domain names because of a new transfer policy inforced by ICANN on the 12th of November 2004, which stated pretty much, that once a transfer was initiated, no one was able to stop the transfer. Registrars like Melbourne IT and Dotsters are just pawns for bigger and smaller enemies, aka hijackers and governing bodies. I have all my domain names with Melbourne IT, and was notified by email that the transfer policy was going to be in place, and procedures to ensure my domain names were locked. I am concerned one of the oldest ISP's in America "PANICS" didn't have there domain name locked (only unlocked with a domain name password). I would also question how this hijacker got the 'victims' password to transfer the licence to another registrar? I definately think people should research facts before they blurt out how horrific the whole scenario is. Any one heard of bureaucratic red tape, I am guessing once Melbourne get's past it they will act accordingly to resolve the issue. Regards, Fully Seriously Sick!

    3. Re:it's worse than that... by SilverspurG · · Score: 3, Funny

      It's called Goodwill.

      Does that still exist? Everything is about the law these days.

      --
      fast as fast can be. you'll never catch me.
    4. Re:it's worse than that... by Anonymous Coward · · Score: 5, Insightful

      I'm just a paralegal, so this isn't legal advice. But I've worked on these cases enough to know what that letter is telling you. First, you need to hire a lawyer to handle this. Second, the letter is telling you the precise steps to take. Follow them like you would command line instructions and you will get the best results.

      Only the new registrar can help. That is your target. Get Dotster to send the Request for Enforcement. Call up and get to know someone at Dotster (and Melbourne) and call and call and call. Be friendly and do all they ask, step by step. Give them all the info you can find about the new person claiming ownership. Look up in Betterwhois and find out who is the new owner. I'm betting dollars to doughnuts, you will find it isn't a real address. Try to contact the new owner by the address, email, phone listed. If you get no response, tell Dotster. Point that out. Find out if the new place is spamming, porn, whatever. That is almost certainly what is happening to your customers. Make clear to the new registrar that they got the domain through lying, trickery, however they got it. Details and proof.

      This is a standard hustle, and usually names change as well as registrars. They generally use more than one hop because it is harder to get it back, harder to trace. Verizon is the worst, in my experience, and they won't help you, but if you can get Dotster and Melbourne on this, they will have to. Make a note of who didn't help you and make future decisions about who you want as your registrar.

      You should be able to get it back, but it may take time.

      Again, the key to it all is get a lawyer. They know exactly how this dance goes. A lawyer who does UDRP. That is what you ask for. It's called domain name hijacking.

  12. You tawkin' ta ME? by Doc+Ruby · · Score: 2, Interesting

    Panix is an old haunt of lots of very savvy New York geeks, particularly security and OS hackers with lots of money and techniques. I'd hate to piss them off, especially with an attitude that merely a planet-width and a foreign law license protects me from my obligation not to screw them.

    --

    --
    make install -not war

  13. MelbourneIT Criminals by Doc+Ruby · · Score: 4, Insightful

    As this post points out, having hijacked panix.com, MelbourneIT could be logging all userID/password logins to shell.panix.com . So Panix customers should all login to the "temporary" replacement, shell.panix.net , and change their passwords ASAP. Then fly to Melbourne with baseball bats.

    --

    --
    make install -not war

    1. Re:MelbourneIT Criminals by Doc+Ruby · · Score: 2, Interesting

      Actually, the circumstantial evidence of the timing doesn't weigh as heavily as the original message, from Thor, in that merit.edu thread, in which he refers to other reason's to be "suspicious". Combine that with the corroboration in this Slashdot thread of exactly this kind of malfeasance by MelbourneIT in the past, and they're looking pretty culpable. Especially in the light of their corporate response: the CEO tells their counsel to tell Panix to get lost, rather than telling a tech to look into the problem.

      MelbourneIT's size and importance are totally irrelevant to their possible guilt. If anything, big, important corporations hide behind their straight appearance to commit the most grevious acts. I'm sure MelbourneIT will get this, especially if they're violating any laws anywhere with this kind of "incompetence", and Panix suffers any losses - likely. Then they'll find out that a gang of jetlagged New Yorkers with baseball bats is the easy way, compared to the lawyers who speak so politely.

      --

      --
      make install -not war

    2. Re:MelbourneIT Criminals by tjls · · Score: 2, Informative
      For what it's worth:

      1) IP addresses are not "part of ssh keys" -- and I can say this with some authority, as the author of one of the first open-source SSH implementations. (Please don't use it here-now-today, it's painfully obsolete!)

      2) SSH clients can store multiple valid keys per DNS name (or, for that matter, per IP address) and multiple physical hosts can have the same SSH private key (the latter, in fact, is probably how Panix should configure its shell servers. Since they provide the same service with the same authentication requirements, using the same SSH key is almost certainly right).

      3) A lot of SSH clients suck, about both these things. To this day, some can't cope gracefully with either condition at all though it's a matter of about 10 lines of code in each case to do so. Even OpenSSH can't deal with the somewhat less common situation of a host having two different keys on two different IP addresses. It's a sad fact that no matter what you do users seem to blindly click through the client's warning messages -- which, I think, disincents developers to get which message appear when exactly right.

  14. pent-up anger by Trepidity · · Score: 4, Insightful

    Michael has irritated a lot of people over the years, so when an opportunity comes up to complain, there's a lot of people who do, and a lot more people who smile and say "finally!"

    (Whether this is a good or bad phenomenon is left as an exercise to the reader.)

  15. Local Action by Doc+Ruby · · Score: 3, Funny

    Anyone in Melbourne with a baseball bat, who wants free drinks the next time they visit New York, want to go "knocking" on MelbourneIT's door?

    --

    --
    make install -not war

  16. Already contacted people by ZenJabba1 · · Score: 2, Interesting

    I know some people in MelbourneIT, and have already spoken to them. They are looking into the issue

    --
    `find / -name "*your_base*" -exec chown us:us {} \;`
    1. Re:Already contacted people by phayes · · Score: 3, Funny

      Your sig forks a process per file, how inefficiant...
      Try using:
      `find / -name "*your_base*" -print | xargs chown us:us`

      --
      Democracy is a sheep and two wolves deciding what to have for lunch. Freedom is a well armed sheep contesting the issue
  17. frontier justice by Anonymous Coward · · Score: 2, Insightful

    I have to post this as an AC but ....

    This is an issue like spam. Frankly, and I doupt Alexis Rosen et all will go this route, but what should happen now is gunshot wounds to the head. My guess is this is a scam to clean out the paypal accounts of panix customers and/or steal domains that are hosted by panix.

  18. Re:If they forgot to renew the domain by BJH · · Score: 2, Insightful

    Nice post - don't bother looking into the facts yourself, just start spouting wild speculation and slander.

    If you'd actually got off your fat ass and done some research, you'd know that the domain did NOT expire, and in fact the registrar still thinks it's registered with them (when it obviously isn't).

  19. Panix.com server looks like a spammers paradise by Chatmag · · Score: 3, Interesting

    Checking the IP that panix.com is on shows several thousand domains, and all seem to have odd names.

    That Las Vegas address used for panix.com is also similar to some used by spammers registering domains, and using a Nevada address in the whois.

    Maybe a check of some of the blocklists will show the panix.com IP listed already. 142.46.200.72

    You could try this link and see if the server is still up. (hint, slashdot effect)

    --
    Pete Carr Owner Chatmag.com
  20. Password Recovery by msaulters · · Score: 4, Informative

    FAILED
    The Melbourne IT Registry Key for Domain Name panix.com was not able to be retrieved. This could be due to the Domain Name being managed by a Melbourne IT Reseller. Please contact your Reseller for assistance. If this fails, please go to our help center.

    www.panix.com is coming up with a freeparking.co.uk web page. This means that SOMEONE is handling DNS for the domain. That is the one piece of useful information in the current whois record. ns1.ukdnsservers.co.uk
    OK, looks like ukdnsservers.co.uk belongs to:
    Domain Name:
    ukdnsservers.co.uk

    Registrant:
    ActiveBytes Software LLC

    Administrative Contact's Address:
    2530 Channin Drive
    Wilmington
    DE
    19810 US

    Registrant's Agent:
    Fibranet Services Ltd [Tag = FIBRANET]

    Relevant Dates:
    Registered on: 25-Mar-2000
    Renewal Date: 25-Mar-2006
    Last updated: 11-Dec-2004

    Registration Status:
    Registered until renewal date.

    Name servers listed in order:
    ns3.ukdnsservers.co.uk 142.46.200.68
    ns4.ukdnsservers.co.uk 207.61.90.197

    This is a company on US soil. If the authorities have been contacted, the FBI should be breaking down these guys' doors right about now, cause they're involved in what could be considered an act of international terrorism, and I'm not being sarcastic. Either ActiveBytes Software, or one of their representatives has knowingly set up DNS records for panix.com, or they have been hacked.

    Unfortunately, it appears that even though their offices may be in Delaware, their DNS is a little farther north:

    traceroute 142.46.200.67
    (Most of traceroute omitted to pass bullshit lameness filter)
    23 145 ms 75 ms 74 ms AL-7304-GigE2.telecomottawa.net [142.46.200.1]
    24 82 ms 85 ms 88 ms 142.46.200.67

    Trace complete.

    traceroute 207.61.90.197
    (Most of traceroute omitted to pass bullshit lameness filter)
    18 65 ms 75 ms 64 ms core1-ottawa23-pos2-2.in.bellnexxia.net [64.230.234.90]
    19 221 ms 204 ms 217 ms ottcorr01-pos5-0-0.in.bellnexxia.net [206.108.99.146]
    20 Request timed out.
    21 244 ms 183 ms 225 ms ns4.ukdnsservers.co.uk [207.61.90.197]

    Trace complete.

    Maybe someone at telecomottawa.net could be contacted to track these people down or help out in some small way. Here's their Customer Care Page They have a toll-free number! Let's see if enough of us call it, or perhaps if enough of Panix's unhappy customers call it, maybe TelecomOttawa will help out (wouldn't it suck if someone were to steal the telecomottawa.net domain name from them in a similar fashion?) Anyway, the TF# is 1-888-424-7771 (X3?)

    Man, this really pisses me off that someone was able to do this, and that these guys aren't having any luck getting the problem fixed.

    --
    These people looked deep into my soul and assigned me a number based on the order in which I joined.
    1. Re:Password Recovery by Legion303 · · Score: 5, Insightful

      "cause they're involved in what could be considered an act of international terrorism, and I'm not being sarcastic."

      Maybe not, but you're sure diluting the living fuck out of the word "terrorism."

    2. Re:Password Recovery by HeghmoH · · Score: 2, Informative

      You can blame various goverments for that, they've been doing it for a long, long time.

      --
      Mod down posts with a "Free Mac Mini/iPod" sig, they're spam!
    3. Re:Password Recovery by dbIII · · Score: 3, Insightful
      they're involved in what could be considered an act of international terrorism
      Terrorists kill people - lets keep some perspective here.
  21. Re:If they forgot to renew the domain by BJH · · Score: 2, Insightful

    Sorry for the thermite reply, but suggesting the oldest ISP on the East Coast can't find their own asses with a flashlight and a map is a bit insulting.

    In any case, I apologise for overreacting.

  22. Not Hypocricy, but Irony by TFGeditor · · Score: 2, Insightful

    This is a superb example of "irony," oft-misapplied on Slashdot, not hypocricy.

    --
    Ignorance is curable, stupid is forever.
  23. Melbourne IT, eh? by pwhysall · · Score: 4, Informative

    Funnily enough, they're the registrar for the scam site http://american-redcross.org/.

    Coincidence? You decide.

    --
    Peter
    1. Re:Melbourne IT, eh? by anttik · · Score: 2, Informative

      True.

      Compare the original and the fake. Fake is missing the navigation bar. Fake's VeriSign verifying thingie leads to validating www.redcross.org instead of american-redcross.org. Notable thing is also that they load images from www.redcross.org to save bandwidth.

  24. They are really old by EssenceLumin · · Score: 2, Funny
    Near the bottom of the page it says -

    We started in 1989, before the advent of the Internet.

    Who knew?

  25. that's true by Trepidity · · Score: 3, Insightful

    But the inverse isn't necessarily true.

  26. panix rules by Anonymous Coward · · Score: 5, Insightful
    note how alexis keeps his cool in this message:
    Hi, all.

    I hate to pop my head up after years of lurking, only when things are going bad, but probably better that than remaining silent.

    First of all, I'm going to be bounced from this list once its cache of my DNS times out, which will probably be in about 2-3 hours, so if you have anything to say that you'd like me to see, please copy me. We're temporarily accepting mail at panix.net in addition to panix.com, so use alexis (at) panix.net.

    A few points to respond to:

    First, Eric, thanks for contacting Bruce and Eric on my behalf. While nothing has happened so far, I hope that it will soon, and in any case I appreciate your efforts to help a total stranger.

    Someone asked if we had registrar-lock set. It's not clear to me what happened. Our understanding is that we had locks on all of our domains. However, when we looked, locks were off on panix.net and panix.org, which we own but don't normally use. It's not clear how that happened; dotster has yet to contact us with any information about, well, anything at all. They did answer a call this morning; they're apprently in the middle of an ice storm. All I was able to larn from them is that according to the person I talked to, they had no records of any transfer requests on our domain from today back through last October.

    Someone suggested invoking a dispute procedure. We'll do that, as soon as we can get someone to actually accept the dispute, but if it goes through that process to completion, many people will suffer, and Panix itself will be tremendously damaged. How long do you think even our customers will stay loyal? (Forever, for many of them, but that doesn't mean the won't be forced to start using a different service.)

    While it's true that MelbourneIT won't do anything before (their) Monday morning, I don't want to paint them as bad guys in this drama. I don't know how they're organized and I don't know how difficult it is for them logistically. Of course I want them to move faster. Much faster. But I'll take what I can get.

    And speaking of MIT, I don't intend to send them "nastygrams" - nor NSI either. Neither of them owes me anything (at least directly) and being heavyhanded would not be a good way to get what I want (restoral of the panix.com domain to dotster) even if I thought they deserved it. I expect that there will be criminal prosecutions arising out of this, but the time for that sort of thing is later, when things are back to normal, and we've fixed any systemic vulnerabilities that can be fixed before they're used to wreak mass havoc. And it's anyone's guess who the target of those prosecutions will be, but I doubt MIT or NSI will be among them.

    Lastly, someone expressed surprise that I'd call MIT's lawyer directly. I didn't. I spent *hours* trying to find working contact info for MIT and Dotster. I didn't find useful 24-hour NOC-type info anywhere. (Someone obviously has this info; I expect it's restricted to a list of registrars.) I reached Dotster's customer support when they opened for business Saturday morning; the guy was polite, and did what he could, but I saw no evidence whatsoever of the promised attempt to assist me after he got off the phone. MIT apparently has no weekend support at all; I finally located their CEO's cellphone in an investor-relations web page. I caled him, and he had his lawyer call me back. That was his choice. FWIW, she's not "just" a lawyer; she's apparently the person who has to make decisions about reverting control of the domain. So she at least needs to be aware of our position. My impression is that she didn't fully grasp the gravity of the situation, and so treated us like she'd treat any other annoying customer who managed to track her down on her day off. This is somewhat understandable (though infuriating) which is why I'd hoped to talk to someone on their tech side first. No luck there, but if any of this reaches them, maybe that will start things going.

    Thanks again to everyone who has tried to help us today.

    /a
  27. Main effect = bad by nurb432 · · Score: 2, Insightful

    Pretty bad when your mail doesnt come to you..

    Espcially if you are business taking orders.. or have the potential for confidential or personal info being in your emails..

    Good thing we all encrypt our mail.. right?

    --
    ---- Booth was a patriot ----
  28. Is *your* company's DNS registered with VeriSign? by philgross · · Score: 3, Insightful

    Verisign has spent big $$$ to advertise its brand as the choice for heavyweight corporate customers. It boggles my mind that they're letting a high-visibility ISP twist in the wind. Talk about brand devaluation.

    Any slashdot reader in coroporate IT should be writing a memo on this and sending it to the CIO/CTO and Legal teams. What will *your* company's registrar do if someone jacks your domain on a weekend? If you're paying the bucks for Verisign, the answer seems to be nada, or maybe they'll write you an infuriating not-out-problem e-mail.

    I think the marketing/sales task for Verisign's competitors just got a notch easier too. Nothing like a good horror story...

  29. very insightful by r5t8i6y3 · · Score: 4, Interesting

    Date: Sun, 16 Jan 2005 10:07:04 +0000
    From: Eric Brunner-Williams in Portland Maine
    To: nanog@merit.edu
    Cc: brunner@nic-naa.net, alexis@panix.net
    Subject: Re: panix.com hijacked (VeriSign refuses to help)

    Oki all,

    Its dawn in Maine, the caffine delivery system has only just started, but I'll comment on the overnight.

    You're welcome alexis@panix.net. If you'll send me the cell phone number for the MIT managment I will call wearing my registrar hat and inform whoever I end up speaking with that Bruce needs to call me urgently, on Registrar Constituency business.

    Next, put a call into the Washingtom Post. They lost the use of the name "washpost.com" which all their internal email used, to due to expiry, so their internal mail went "dark" for several hours. This was haha funny during the primary season (Feb 6). If they don't get it try the NYTimes. Put the problem on record. There is an elephant in the room.

    The elephant is that the existing regime is organized around protecting the IPR lobby from boogiemen of their own invention. They invented the theory that trademark.tld (and trademark.co.cctld) existence dilutes the value of trademark, hence names-are-marks, bringing many happy dollars (10^^6 buys) into the registrar/registry system ($29-or-less/$6, resp., per gtld and some cctlds), and retarding new "gTLD" introductions, as each costs the IPR interests an additional $35 million annually.

    To solve their division of spoils problem, is "united.com" UAL or is it UA?, we had DRPs, which is now a UDRP, and more DRPs for lots of cctlds.

    These [U]DRPs take many,many,many,many units of 24x7. They were invented for the happy IPR campers, who care about _title_, not _function_. If the net went dark that would be fine with them to, so long as the right owners owned the right names.

    Restated, there is no applicable (as in "useful for a 24x7 no downtime claimant") law in the ICANN jurisdiction.

    And it is your own damn fault. Cooking up the DRPs took years of work by the concerned interests, and they were more concerned with enduring legal title then momentary loss of possession. During those years, interest in the DNSO side of ICANN by network operators went from some to zero, and at the Montevideo meeting the ISP and Business constituencies were so small they meet in a small room and only half the seats were taken. After that point they were effectively merged. IMHO, Marilyn Cade and Phillipe Shepard are the ISP/B Constituency, and they can't hear you (for all 24x7 operational values of "you").

    In case it isn't obvious, the "your own damn fault" refers to a much larger class of "you" than Alexis Rosen.

    [Oh, the same happy campers are why :43 is broken. They want perfect data at no cost and w/o restriction. Registrars don't want slamming, today's owie, and registrants don't want spam (which some ISPs do), so the whole :43 issue is a trainwreck of non-operational interests overriding operational interests. Registrars would be happy to pump :43 data to operators, if we could manage the abuse, instead we get knuckleheads who insist that spam would be solved forever if ...]

    There is a fundamental choice of jurisdictions question. Is ICANN the correct venue for ajudication, or is there another venue? This is what recourse to the "ask a real person" mechanism assumes, that talking to a human being is the better choice.

    Bill made this comment:

    > Since folks have been working on this for hours, and
    > according to posts on NANOG, both MelbourneIT and
    > Verisign refuse to do anything for days or weeks,
    > would it be a good time to take drastic action?
    >
    > Think of what we'd do about a larger ISP, or the
    > Well, or really any serious financial target.
    >
    > Think of the damage from harvesting logins and
    > mail passwords of panix users.

    You (collectively) are

    1. Re:very insightful by rs79 · · Score: 3, Informative

      "And it is your own damn fault. Cooking up the DRPs took years of work by the concerned interests, and they were more concerned with enduring legal title then momentary loss of possession. During those years, interest in the DNSO side of ICANN by network operators went from some to zero, and at the Montevideo meeting the ISP and Business constituencies were so small they meet in a small room and only half the seats were taken. After that point they were effectively merged. IMHO, Marilyn Cade and Phillipe Shepard are the ISP/B Constituency, and they can't hear you (for all 24x7 operational values of "you")."

      It's *our* fault? Nice try, Eric. I should fly halfway around the world 4X a year at 5 grand a pop to stay in the ICANN 4 or 5 star host-hotel so I get my 15 minutes of being ignored at the mcirophone? BTDT for a couple of years. Even if you think you scored a minor victory ICANN will, and has, quietly chaged the bylaws to circumvent that. Oh, but don't worry, as a membership organization, as dictated by the USG we can all vote on this. Oh that's right, that bit never happened even though ICANN's initial purpose was to only define the organizaion, get members then pass it off to the duly elected board. We still have the current IBM/Magaziner appointed board and the "members" don't exists.

      Lesse here, on one side we have the Intellectual Property wonks who ARE funded to fly to every meeting and are paid full time to lobby ICANN. Those buggers are everywhere, do not operate in the open and are anything but transparent. They work for companies with 3 letter names.

      On the other side we have "us" and "our funding" (hahahahah). We lose. Thanks for playing; tragedy of the commons.

      Interest in the DNSO and ICANN has waned because people are tired of beating their head against a brick wall till it's a bloody pulp; you can't begin to fight the behind the scenes back channel closed shenanigans the IP folks play, you don't even find out what they are till years later (cf the secret, thou shall not disclose meeting that IBM arranged with ICANN and NSI that Farber and Cerf attended that set this all in motion). They and they alone, as correctly pointed out, are and have always been the boogeymen behind virtually all troubles in the DNS today and have been since long before ICANN was a glint in Joe's eye.

      To paraphrase Mark Twain, "It's a good thing we don't get all the ICANN we pay for"

      Look what happened to Aurbach. ICANN see's openness as a fault and routes around it.

      --
      Need Mercedes parts ?
  30. preventable by john_uy · · Score: 2, Insightful
    if we use dnssec. i read an article just this week about the integrity of the dns. initially, i thought that why would you need this type of implementation - here comes the reason. we can see it happen more. by using dnssec, in theory it should be able to "legitimize" dns requests and verify their authenticity before changes are being made to dns records. in this case, 3rd party will not be able to change the records because they will not have the private key from panix, for example.


    this technology is new but this type of scenarios should speed things up in making it a requirement for dns deployments.

    --
    Live your life each day as if it was your last.
    1. Re:preventable by tjls · · Score: 2, Informative

      It's not clear that DNSSEC actually would stop this particular kind of attack -- which is one reason why it's so nasty (the attack, not DNSSEC!).

  31. Hello, NY Times? by wytcld · · Score: 4, Interesting

    Panix at least used to have a lot of users with jobs like "NY Times reporter" and "Wall Street technology analyst." This story needs to be amplified to the point where there's a total restructuring of the domain registration system, one which removes Network Solutions entirely from the business. Can we assume that Panix users will be doing their part to play this up in the mainstream media capital of America?

    --
    "with their freedom lost all virtue lose" - Milton
  32. whois.melbourneit.com by pureone · · Score: 2, Informative

    whois south-parsonalbanking.com

    Whois Server Version 1.3

    Domain names in the .com and .net domains can now be registered
    with many different competing registrars. Go to http://www.internic.net
    for detailed information.

    Domain Name: SOUTH-PARSONALBANKING.COM
    Registrar: MELBOURNE IT, LTD. D/B/A INTERNET NAMES WORLDWIDE
    Whois Server: whois.melbourneit.com
    Referral URL: http://www.melbourneit.com
    Name Server: YNS1.YAHOO.COM
    Name Server: YNS2.YAHOO.COM
    Status: ACTIVE
    Updated Date: 15-jan-2005
    Creation Date: 15-jan-2005
    Expiration Date: 15-jan-2006

    >>> Last update of whois database: Sun, 16 Jan 2005 07:38:23 EST

    NOTICE: The expiration date displayed in this record is the date the
    registrar's sponsorship of the domain name registration in the registry is
    currently set to expire. This date does not necessarily reflect the expiration
    date of the domain name registrant's agreement with the sponsoring
    registrar. Users may consult the sponsoring registrar's Whois database to
    view the registrar's reported date of expiration for this registration.

    TERMS OF USE: You are not authorized to access or query our Whois
    database through the use of electronic processes that are high-volume and
    automated except as reasonably necessary to register domain names or
    modify existing registrations; the Data in VeriSign Global Registry
    Services' ("VeriSign") Whois database is provided by VeriSign for
    information purposes only, and to assist persons in obtaining information
    about or related to a domain name registration record. VeriSign does not
    guarantee its accuracy. By submitting a Whois query, you agree to abide
    by the following terms of use: You agree that you may use this Data only
    for lawful purposes and that under no circumstances will you use this Data
    to: (1) allow, enable, or otherwise support the transmission of mass
    unsolicited, commercial advertising or solicitations via e-mail, telephone,
    or facsimile; or (2) enable high volume, automated, electronic processes
    that apply to VeriSign (or its computer systems). The compilation,
    repackaging, dissemination or other use of this Data is expressly
    prohibited without the prior written consent of VeriSign. You agree not to
    use electronic processes that are automated and high-volume to access or
    query the Whois database except as reasonably necessary to register
    domain names or modify existing registrations. VeriSign reserves the right
    to restrict your access to the Whois database in its sole discretion to ensure
    operational stability. VeriSign may restrict or terminate your access to the
    Whois database for failure to abide by these terms of use. VeriSign
    reserves the right to modify these terms at any time.

    The Registry database contains ONLY .COM, .NET, .EDU domains and
    Registrars.

    Domain Name.......... south-parsonalbanking.com
    Creation Date........ 2005-01-15
    Registration Date.... 2005-01-15
    Expiry Date.......... 2006-01-15
    Organisation Name.... Douglas Hurcomb
    Organisation Address. 1516 Hidden Valley Ln
    Organisation Address.
    Organisation Address. Rochester
    Organisation Address. 48306
    Organisation Address. MI
    Organisation Address. UNITED STATES

    Admin Name........... Douglas Hurcomb
    Admin Address........ 1516 Hidden Valley Ln
    Admin Address........
    Admin Address........ Rochester
    Admin Address........ 48306
    Admin Address........ MI
    Admin Address........ UNITED STATES
    Admin Email.......... douglashurcomb@yahoo.com
    Admin Phone.......... +1.2486568102
    Admin Fax............

    Tech Name............ YahooDomains TechContact
    Tech Address......... 701 First Ave.
    Tech Address.........
    Tech Address......... Sunnyvale
    Tech Address.........

    --
    120 chars is not bloody enough for a real sig!!! you bastards even count spaces!!!
  33. Panix.com WAS locked, moved anyway by Burdell · · Score: 3, Informative

    Panix thought that they had all of their domains in registrar-lock status. When they checked panix.net and panix.org after panix.com got swiped, they were no longer locked.

    However, this has nothing to do with them being locked or not. The registrar Panix uses is Dotster, and they show no record of panix.com being transferred. In other words, Verisign (who is in charge of all .com registrations) allowed a domain to be transferred to a different regsitrar without following the published procedures. Even if a domain is not locked, there is a notification and waiting period that was ignored. Somehow MelbourneIT and Verisign short-circuited the system (quite possibly an inside job at both).

    IIRC the .net control is up for renewal soon and other companies may bid to take it away from Verisign; let's hope that happens (my main domains are all .net).

  34. Hey, my domain was stolen the other week too by maugt · · Score: 5, Insightful

    This does happen a lot more than you think. I started a blog to document it at Orangelimey.blogs.com

    NSI is currently claiming that the transfer was legitimate - somehow the hijacker got into the administrative contact's email and compromised the accounts - how we still don't know. However, the person that ended up with the domain seems to be willing to give it back.

    Really, the whole domain security thing is ridiculous. For a domain (which is considered property under a ruling from the appeals court in the sex.com case) to be transfered with such lax legal proceedings is pathetic. Can I steal your car or your house by simply faking email and guessing passwords? Of course not.

    Maybe panix can make enough of a stink about this to get someone to stand up and take notice - although who can do this I don't know. ICANN is toothless and only cares about trademark disputes.

    Someone told me as a result of this that 40,000 domains were hijacked in the last year. I don't know where this data comes from, but really, obviously something is wrong.

    Feel sorry for panix, I used them when I lived in NYC

    1. Re:Hey, my domain was stolen the other week too by HiThere · · Score: 2, Insightful

      I'm not sure that ICANN is toothless at all. I suspect their interests just lie elsewhere.

      Whatever happened to the election of the ICANN board? Trust them? For anything? After that?

      --

      I think we've pushed this "anyone can grow up to be president" thing too far.
  35. ICANN: a slow moving parody of itself. by rs79 · · Score: 2, Insightful

    Exsqueeze me? One of the biggest registrars that a lot of poeple have had trouble with is CLOSED for the weekend?

    I run a bunch of (free) mailing lists and DNS for a variety of stupid things like cars, tropical fish, dns etc. I'm open 24/7 and get calls at 4:30 am, not happily, but I do fix stuff. That MIT as a multimillion dollar organization thinks it's ok to take the weekend off critical internet infrastructure should be enough to get their precious ICANN accreditation yanked. But given how much money MIT pays ICANN this will never happen.

    Expect fully a press release from ICANN saying how responsive MIT was in this situation.

    Welcome to the modern internet.

    --
    Need Mercedes parts ?
  36. Panix mail accessible! by howardcohen · · Score: 3, Informative

    I *am* getting my panix.com mail by going to mail.panix.NET, and using their web-based mail client.

    By way of background, I've been a Panix user for more than a decade. They are classy, intelligent people, which sets them apart from most folks in their line of work.

  37. Re:Deal with the Devil by tjls · · Score: 5, Informative
    Nice try, troll.

    To answer your "questions", no and no.

    Panix has been deeply involved in efforts to promote and protect Internet security since, I'd wager, long before you even had access to the Internet at all. I should know -- within two months of my first coming to work at Panix in 1993 the majority of my work was shifted from normal system administration to security.

    The very first NY Times article (possibly the first national newspaper article at all) on the subject of Internet security featured Panix' heroic efforts to publicize and mitigate a series of network sniffer attacks that had been previously kept under wraps, and compromised the security of thousands of Internet users (at a time when the total population of the Internet was only a few tens or perhaps hundreds of thousands). Panix played a key role in the emergence of full-disclosure security lists by refusing to sit still while vendors and CERT (don't get me wrong. CERT is good. They just weren't then) conspired to cover up known vulnerabilities for years at a time. And so forth.

    To this day, security remains a major focus at Panix. It has to -- they're the oldest, most prominent, and one of the largest (if not the largest) shell ISPs still out there, and their users won't tolerate system outages caused by security failures, or security failures that compromise those users' own security. In general, if you find Unix timesharing systems the size of Panix, they're at universities; and look at those folks' security records. Panix, on the other hand, is worlds better.

    To respond to your other happy fun mudslinging, Panix has not and does not tolerate "online crimes" by its users, whether your invented "user" Kevin Mitnick or anyone else. Never did, doesn't now; security is important to Panix; it is essential to their business; and so is the health of the Internet itself.

    Depending how you count, Panix is the second or third oldest consumer ISP in the world. Panix has been around long enough to remember the times when if they had a security incident, a significant fraction of the Internet shuddered (e.g. when we were offline for two days for security reasons in 1994, traffic on Usenet as a whole fell considerably). It would be hard to find any business on the Internet more fundamentally concerned that its own security problems not impact others than Panix has been, and is.

    Which, of course, is quite a different attitude than that exemplified by some other businesses mentioned in this thread.

  38. no, it's a good thing by frovingslosh · · Score: 2, Insightful
    what a sad state of affairs when it's trivial to hijack a domain, but it takes an act of god to return it to its rightful owner. apparently, even law enforcement can't get verisign or melbourneit to do squat:>/I>

    I think it's good that the response was what it was. After the lawsuits service providers like verisign will have learned an important lesson. Had they just put things back and said "opps" the chance to teach them them the importance of not letting this happen in the first place might have been lost.

    --
    I'm an American. I love this country and the freedoms that we used to have.
  39. UPDATE by rs79 · · Score: 2, Informative

    Berryhill went to the house in Wilmington. The address is bogus.

    Or rather the address is real but the guy we're looking for doesn't live there any more and the poeple there get all "sorts of wierd things".

    This apparanly is not the first time this happened.

    The lawyer in question has moved to PA.

    John's gong home to check state corporate registration records to try to find him.

    --
    Need Mercedes parts ?
  40. This just in!!! by Anonymous Coward · · Score: 5, Informative

    (Posted by Ed Ravin [staff]) Sun, Jan 16 2005 -- 5:41 PM
    ----------------
    Recovery is underway from the panix.com domain hijack.

    The root name servers now have the correct information, as does the WHOIS registry. Portions of the Internet will still not be able to see panix.com until their name servers expire the false data. More info soon.

    -- Ed