[77244] in North American Network Operators' Group
Panix.com should be back.
daemon@ATHENA.MIT.EDU (Majid Farid)
Sun Jan 16 22:58:10 2005
Date: Sun, 16 Jan 2005 22:57:54 -0500
From: "Majid Farid" <MajidFarid@TelecomOttawa.com>
To: "nanog list" <nanog@merit.edu>
Errors-To: owner-nanog-outgoing@merit.edu
I see that DNS changes has been reverted
http://www.dnsreport.com/tools/dnsreport.ch?domain=3Dpanix.com
I have also contacted our Customer owner of ns1.ukdnsservers.co.uk
[panix.com] (142.46.200.67) they have assured me they will remove the
DNS config as well.=20
Sorry for the last response I was away for weekend.=20
--
Majid Farid
Telecom Ottawa Limited.
-----Original Message-----
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of
Gadi Evron
Sent: Sunday, January 16, 2005 7:24 PM
To: nanog list
Subject: domain hijacking - what do you do to prepared?
Until today, I considered this to be a real and relevant threat,=20
although rather low in my matrix.
As someone I know said today, now that kiddies saw how much "fun" this=20
is, I am sure they will attempt this again.
The question that comes to mind is - what do you do to be prepared?
I suppose that other than setting registrar lock in place, there is=20
another thing one can do.
Study!
Whether it's checking the expiration date for your domain, establishing=20
contact with your up-in-line authority - registrar, tld, etc. depending=20
on who you are.
Having the relevant contact information at hand, establishing a set=20
policy on how to handle such an incident and who to contact, bugging=20
your next-in-chain about setting a policy on this with you, as well as=20
setting such a policy for those who are slaves to you.
That said, all that is left now is to see how this happened (so that it=20
won't happen again - just killing a fire doesn't mean it won't be=20
re-ignited) and perhaps think a bit on how we do things - which I am=20
sure many will now do.
Maybe this can be another discussion issue for the next NANOG=20
get-together as well?
Gadi.
