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.
;)