comment on

For some this is relatvely old news, as the change dates from 15th Sept 2003. In case you don't yet know (or sort of know but have not really considered what it means) - Have a look at this Installing Email::Valid or try this:

use Socket;
for ( 0..100 ) {
    $domain = "i-am-a-domain-that-should-not-resolve-but-i-will-$_.com
+";
    $ip = inet_ntoa(inet_aton($domain));
    print "$domain\t$ip\n";
}
__DATA__
i-am-a-domain-that-should-not-resolve-but-i-will-0.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-1.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-2.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-3.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-4.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-5.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-6.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-7.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-8.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-9.com    64.94.110.11
i-am-a-domain-that-should-not-resolve-but-i-will-10.com    64.94.110.1
+1
[download]

If you are trying to validate that a domain exists Verisign have now ensured that it will appear to exist at 64.94.110.11 (unless it really does exist) If this IP stays the same it is at least a fixable issue. If you are currently doing anthing that checks to see if a domain exists and splits logic if it does not it will now be totally broken. Just some to the code that will now not behave as expected:

Net::DNS (will always resolve a .com or .net domain)
Email::Vaild (all .com/.net domains are now valid, even if they are totally fake)
inet_aton()
gethostbyname()

There is a discussion of the ramifications here There are a number of DNS server patches already out http://lists.insecure.org/lists/bugtraq/2003/Sep/0276.html

Update thanks Moriarty

This only affects TLDs controlled by Verisign et al, but as that includes .com and .net we are not talking about a small problem.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

In reply to Verisign Hijack all possible .com .net domains and destroy Email::Valid, Net::DNS, gethostbyname() etc by tachyon

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks