full-disclosure - What to do with a "burned" dns record? (was: sco.com -> slow? :)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <401D85E8.5020206@gmx.net>
From: besh at gmx.net (Benjamin Schweizer)
Subject: What to do with a "burned" dns record? (was:
 sco.com -> slow? :)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mary Landesman wrote:

| Can anyone shed light on this, i.e. why caldera.com would be
| affected if the DNS entry for sco.com were removed?

caldera.com, www.caldera.com, sco.com and formerly www.sco.com pointed
to the same ip address. The DDoS had success and this machine is
burning. As someone else mentioned: look at [1].
I assume that the DNS entry is still cached on some networks and the
SCO admins will bring up their domains by monday (except www.sco.com).

The big question is: what will happen to this "burned" domain name? It
will need months till this packetstorm will calm. Is there a more
professional idea than removing the a records?

[1] http://uptime.netcraft.com/perf/graph?site=www.sco.com

- --
"Men can only be happy when they do not assume that the object of life
is happiness."                                       --George Orwell
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAHYXo4Lmwv7NFcKMRAqakAJ0dvzQ/3coIDqKf0bXuIeovtNXhKgCgl54q
eI4iTmzuMDySLmnRiPGgEes=
=5PmV
-----END PGP SIGNATURE-----