-----BEGIN PGP SIGNED MESSAGE----- Tim Wilde wrote:
On Tue, 16 Sep 2003, Niels Bakker wrote:
A wildcard A record in the net TLD.
$ host does.really-not-exist.net does.really-not-exist.net has address 64.94.110.11
$ host 64.94.110.11 11.110.94.64.IN-ADDR.ARPA domain name pointer sitefinder-idn.verisign.com
It even responds on port 25 (says 550 on every RCPT TO). Gah.
Even worse of this is that you can't verify domain names under .net any more for 'existence' as every .net domain suddenly has a A record and then can be used for spamming... From: Spammer <i@spam.using.verisign.eventhoughthisdomaindoesntexist.net> To: You <spamtarget@example.com> Thank you Verisign! Now we need to check for existence of an MX and then just break a couple of RFC's in the process :(
It's Verisign's return shot at the web browser "couldn't find this page" searches. Doesn't seem to have much by way of advertising yet, but I'm sure that'll change. I heard about this coming from somewhere last week, though I don't recall where. Probably Wired or the WSJ. Verisign wants the revenue that all those typos are generating. It's just the next shot in the eyeball war.
Who said the internet wasn't commercial again ? Thank you goverment of the United States of America for allowing such money hungry organisations to abuse one of the original tld's. Wasn't .net meant for *networks* ? aka ISP backbone infrastructure and not for commercials? (And I thought that domain reselling was a yucky business) Greets, Jeroen -----BEGIN PGP SIGNATURE----- Version: Unfix PGP for Outlook Alpha 13 Int. Comment: Jeroen Massar / jeroen@unfix.org / http://unfix.org/~jeroen/ iQA/AwUBP2ZIvCmqKFIzPnwjEQLQkgCgtFDU1TKOrt/tz0I+GGm+Vu/P+xUAoI+s 6Czvls9qXOslOkOnJXLhU8ZC =sC7+ -----END PGP SIGNATURE-----