Non existant domain names now resolve to Verisign!

Team Member Joined: 06 Jan 2002 Posts: 2564

Boy does this drive me mad... Twisted Evil

http://slashdot.org/articles/03/09/16/0034210.shtml?tid=126&tid=95&tid=98&tid=99

Let's just hope they stop this ASAP, either because they get DoSed or because they're forced to by the government...

Edit: Ah, at least someone has done the right thing Smile

http://www.whois.sc/news/2003-09/verisign-sued.html

Team Member Joined: 06 Jan 2002 Posts: 2564

Hmm... One thing I just remembered is that Verisign has been doing something similar for .cc domains for ages. Except that the page is even more "commercial": it has a link to buy the domain! Rolling Eyes

Posted: Sat Sep 20, 2003 8:15 pm (20 years, 7 months ago)

And they've been allowed to get away with this because... ? Rolling Eyes

Posted: Tue Sep 23, 2003 3:16 pm (20 years, 7 months ago)

seems like another step towards idiot-proofing computers (and by that I mean people who can't understand the errors are idiots, not people who can't type Wink

)

/me sighs, goes back to coding

Team Member Joined: 06 Jan 2002 Posts: 2564

If you want to idiot proof computers, make it so that the browser produces this search page, not Verisign! Then you can choose to not have this dumb search page (I actually got my router to block the IP Very Happy

, but I still get a "blocked page" warning Sad

).

Posted: Fri Sep 26, 2003 4:33 pm (20 years, 6 months ago)

lol...can you make your router route packets for the IP to, say, 192.168.0.1 instead? that'd get rid of it's warning

Team Member Joined: 06 Jan 2002 Posts: 2564

No, I can't, but I guess I could modify the hosts file... Smile

Posted: Fri Sep 26, 2003 5:34 pm (20 years, 6 months ago)

can you do that for an IP?

Team Member Joined: 06 Jan 2002 Posts: 2564

No, you're right, but you can point sitefinder.verisign.com to 192.168.0.1 Smile

Posted: Sat Sep 27, 2003 9:23 am (20 years, 6 months ago)

ahh, cool