Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Verisign DNS Tragedy - * -> 64.94.110.11 (Read 5107 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Verisign DNS Tragedy - * -> 64.94.110.11

[deleted]

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #1 –
Erm... sorry, but I don't understand what's going on here.

What's the deal with 64.94.110.11?

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #2 –
Verisign now own virtually any unregistered .com/.net domain name.

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #3 –
Any solution available for us Windows 2k/2k3 DNS Users? (Which are forced to use it because of active directory etc?)
You can fool some of the people all of the time, and all of the people some of the time, but you can not fool all of the people all of the time.

- Abraham Lincoln

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #4 –
Quote
Verisign now own virtually any unregistered .com/.net domain name.

wow...

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #5 –
How is that any worse than Microsoft poping up - on MSN it cannot find the domain (for Internet Explorer Users)?

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #6 –
This affects more than just web browsers.


Example: All those spam messages that come from bogus .com and .net addresses? All those domains are now valid, thanks to Verisign. Unless, of course, your DNS servers are patched against this nonsense.

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #7 –
Any information on HOW that happened? An article link or something?

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #8 –
Check out this news at SlashDot

And some discussion at NANOG

IMO, Verisign should be banned on managing TLD. They should be forced to hand over their administration of the root ns to a competent not-for-profit organization.
-- Floydian Slip

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #9 –
Quote
I'd be impressed to see someone hack 64.94.110.11 and redirect traffic to www.goatse.cx.

goatse.cx? Who links to goatse.cx these days? Today's real trolls link to tubgirl.comtubgirl.com.

Note: Do not click that link if you do not want to be disgusted. Seriously.



    Ack. This DNS thing really sucks. However, it seems as though it hasn't propagated to me yet; misspelled domains still give a normal error here.

Edit: Wow... HA filters out tubgirl links. Cool.

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #10 –
Quote
Erm... sorry, but I don't understand what's going on here.

What's the deal with 64.94.110.11?

I was thinking the same thing when I read it yesterday.

So, could this be the root of DNS problems?
I've had some weird crap happening with my ISP with the DNS server magically going down everyday, and websites not being responsive or not loading.

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #11 –
I found this explanatory rant to be pretty informative for me.

http://www.haque.net/verisign_dns_rant.php

[edit] Especially the part about their logging of mistyped URL's containing personal info was interesting [/edit]
 

Verisign DNS Tragedy - * -> 64.94.110.11

Reply #12 –
Seems like my ISP has already taken care of this brain damage.

/EDIT\
Spoken too soon - got my DNS cache record.
\EDIT/
ruxvilti'a