Date: Tue, 16 Sep 2003 20:28:20 -0400 From: Michael Edenfield <kutulu@kutulu.org> To: "M. Warner Losh" <imp@bsdimp.com>, jdp@polstra.com, dan@langille.org, freebsd-hackers@freebsd.org Subject: Re: Any workarounds for Verisign .com/.net highjacking? Message-ID: <20030917002820.GD84494@wombat.localnet> In-Reply-To: <20030916142052.B28748@tikitechnologies.com> References: <3F673E27.29338.6E87ACC@localhost> <XFMail.20030916145304.jdp@polstra.com> <20030916.175558.10083602.imp@bsdimp.com> <20030916142052.B28748@tikitechnologies.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--8nsIa27JVQLqB7/C Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Clifton Royston <cliftonr@tikitechnologies.com> [030916 20:22]: > I found most of the discussion seems to be going on on NANOG.=20 > (Apparently they're not the first, BTW; some CC TLDs have been doing it > for a while, as have some of the new TLDs like .museum. It's just that > it was a noise-level problem until it affected .com and .net) In particular, many of the countries where domain names are their "primary export" (think .nu, .cc, etc) do this. Some of them have seperate MX records, too, so all mail to non-existant domains gets shunted off somewhere. On the flip side, the people who run .bix and .info (?) tried the same stunt as Verisign a few months back, and if I remember my news blurbs right, the US Gov't asked them to stop. --Mike --8nsIa27JVQLqB7/C Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/Z6qjCczNhKRsh48RAmsnAJ4vdT+qJ/v11t4uhh/3ilnu+QgOCwCgoaJZ OduudHH7I/WAUGkecY8gJrI= =z5eD -----END PGP SIGNATURE----- --8nsIa27JVQLqB7/C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030917002820.GD84494>