GoFuckYourself.com - Adult Webmaster Forum - Verisign - getting all typo and expired domain traffic?

- Fucking Around & Business Discussion (https://gfy.com/forumdisplay.php?f=26)

- - Verisign - getting all typo and expired domain traffic? (https://gfy.com/showthread.php?t=174864)

Quote:

Originally posted by kad
Versign is Wildcarding .com and .net.

You used to be able to do something like this before Verisign steped in. The best way to describe it is in a geeky conversation..

Client Machine (looking for www.gofuckyourself.com) : Hello ns1.gofuckyourself.com, do you happen to know where www.gofuckyourself.com is?

Server (ns1.gofuckyourself.com): Well yes i do! Its at 64.88.blah.blah. Hey, while your here, did you know that I can also resolve any domains for . ? Pretty cool huh?

Client Machine : Wow. Ill remember that. Thanks.

End of conversation.

Anyhow, when the client doesnt get a response from its primary NS, it now remembers "Fuck, ns1.gofuckyourself.com might be able to help out". So it asks ns1.gfy and it ALWAYS responds "Yep, micr0s0ft.com resolves to 64.64.55.11". Now ns1.gfy has control of all your type ins.

Ive seen this work, one of my co-workers at another company I used to work for did this by accident. Fun until people complain :)

Im pretty sure noone will understand what im rumbling on about, but I feel good that I got this out of my system.

Yes, this was possible.
But only on people running a certain broken version of the Windows NT domain server.

So most ISP users were not affected.

bumping again, tis a hot issue

Verisign is a BAD compagny :)

verisign is such a shitty company. Anyone remember when they were sending fake renewal notices to hi-jack domains?

http://www.gofuckyourself.com/showth...ghlight=domain

Most people use the DNS servers which was given to them by their provider, arn't those providers able to change/block this?

At my provider I still get the standard NO DNS error when I type a non existent domain name.

I've been reading a few different ISP mailing lists, some of them are already making slight code changes to their DNS cache daemons to convert the Verisign IP into the correct "no domain exists" response.

Heh heh, you can poison the text used on their page by changing some data in the URL...

http://sitefinder.verisign.com/lpc?u...0cock%3C/h1%3E

Quote:

Originally posted by strobi
buying stock NOW!

up 3.74% today already
not bad

too bad i'm not into stocks (yet)

a good argument would describ how this is actually copyright infingment

50 Bitches :glugglug

www.bagdadxxx.com also :1orglaugh

Quote:

Originally posted by Why

and whoever started this thread... apparently verisign only takes the web traffic, they have no MX entries in the dns zones for all of those, so it really doesnt effect mail for expired/unregistered domains.

Um actually it does affect mail servers.

<[email protected]>:
64.94.110.11 does not like recipient.
Remote host said: 550 User domain does not exist.
Giving up on 64.94.110.11.

--- Below this line is a copy of the message.

The IP address returned is 64.94.110.11, which reverses to sitefinder.verisign.com

All RFC-compliant mail servers will follow up a negative MX response with an A lookup and connect to that IP, if you send mail to a bogus domain (.com or net), it goes to verisign's server where there is a something called snubby rejecting all mail.

So it doesn't matter if there isn't a MX record. Verisign is advertising a A record which compliant Mail Servers are checking, and connecting to just like they are suppose to be.

Go ahead fire up hotmail and send a message to a bogus email address at obviously bogus domain.com and domain.org.

Compare where the bounces come from.

The .org will come from your local mail server. The .com will be coming from verisigns server.

;)

Quote:

Originally posted by Why
rr.com has null routed the IP they are using to land all those on.

way to go.

and whoever started this thread... apparently verisign only takes the web traffic, they have no MX entries in the dns zones for all of those, so it really doesnt effect mail for expired/unregistered domains.

the resolving server sitefinder-idn.verisign.com (64.94.110.11) accept connections on port 25