If you've been following the news as of late, VeriSign has decided to resolve all non-existent domain names to a service they set up called Site Finder in a scheme to take advantage of their monopoly as controllers of the .com and .net TLDs. This is particularly annoying for individuals who enjoy checking the validity of links (I send a header that is the same as what IE 6.0 would send). As is shown by the following link, if the domain name doesn't exist (expired or was entered by someone who just wanted to dump trash into your database) then it will return a valid page (after a 302 moved header): http://www.lsadjflj.com/alksdjf/aldhgjh.
Enter Acme::DNS::Correct to correct this problem. It is designed as a drop-in replacement for Net::DNS::Resolver. If the ip for the Site Finder site is detected, the response will be cleansed of the offending ip. The only bug in this module is in the case where you actually wish to resolve sitefinder-idn.verisign.com.
-
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.
|
