Date: Tue, 16 Sep 2003 14:20:53 -1000 From: Clifton Royston <cliftonr@tikitechnologies.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: jdp@polstra.com Subject: Re: Any workarounds for Verisign .com/.net highjacking? Message-ID: <20030916142052.B28748@tikitechnologies.com> In-Reply-To: <20030916.175558.10083602.imp@bsdimp.com>; from imp@bsdimp.com on Tue, Sep 16, 2003 at 05:55:58PM -0600 References: <3F673E27.29338.6E87ACC@localhost> <XFMail.20030916145304.jdp@polstra.com> <20030916.175558.10083602.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 16, 2003 at 05:55:58PM -0600, M. Warner Losh wrote: > I think we should put a filter for this nonsense into the base > system. Hack the resolve to filter out the adddress, and hack bind to > filter it out too. that way we can leverage our position in the name > servers in the world to do something about this BS. IMHO the correct behavior would be to discard any wildcard RR at any TLD zone. I found most of the discussion seems to be going on on NANOG. (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) The ISC has announced it expects to have a patch by Wednesday. That's better than I'd hoped. Thanks for all the feedback I've got, BTW. <http://apnews.excite.com/article/20030916/D7TJOF3G0.html>; -- Clifton -- Clifton Royston -- cliftonr@tikitechnologies.com Tiki Technologies Lead Programmer/Software Architect Did you ever fly a kite in bed? Did you ever walk with ten cats on your head? Did you ever milk this kind of cow? Well we can do it. We know how. If you never did, you should. These things are fun, and fun is good. -- Dr. Seuss
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030916142052.B28748>