Item Description: Return expected results when attempting to perform a DNS lookup on domains that don't exist
Review Synopsis:
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.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Acme::DNS::Correct
by DrHyde (Prior) on Sep 22, 2003 at 19:38 UTC | |
by Anonymous Monk on Sep 23, 2003 at 00:01 UTC | |
Re: Acme::DNS::Correct
by atcroft (Abbot) on Sep 23, 2003 at 03:56 UTC | |
Re: Acme::DNS::Correct
by taint (Chaplain) on May 25, 2014 at 20:15 UTC | |
by soonix (Canon) on May 25, 2014 at 21:49 UTC | |
by taint (Chaplain) on May 25, 2014 at 23:46 UTC |