Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling
 
PerlMonks  

Acme::DNS::Correct

by antirice (Priest)
on Sep 22, 2003 at 16:59 UTC ( [id://293188]=modulereview: print w/replies, xml ) Need Help??

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
    After seeing this module on CPAN, I am sorely tempted to write Acme::DNS::Correct::Corrected, which would apply the same algorithm as is used by the BIND patch. But ICBA.

    Update: this isn't meant as criticism of Acme::DNS::Correct, BTW

      Please note that not everyone runs their own DNS server. For those individuals, this is a very nice option since it seems you can start running it with little modification to the scripts that use Net::DNS::Resolver.

      Anonymously yours,
      Anonymous Nun

Re: Acme::DNS::Correct
by atcroft (Abbot) on Sep 23, 2003 at 03:56 UTC
    My only question would be does it only deal with the Verisign wildcards (.com and .net), or does it handle the others as well (such as those mentioned elsewhere, such as in the djbdns patch)? Just from reading the docs for it, it does not look as if it does, appearing to be limited to only the Verisign address. If this is indeed the case, then perhaps it should be updated to handle the others as well?
Re: Acme::DNS::Correct
by taint (Chaplain) on May 25, 2014 at 20:15 UTC
    Greetings, Monks.

    While I realize this review is quite old now. What follows is quite pertinent today, as it would have been at the time this review was created.

    Verisign aka; Network (Po|So)lutions, received quite a bit of push-back on this; both from the Standards (ICAN|IANA) organizations, as well as DNS providers. In the case of DNS providers, many, opted to NUKE the Versisgn tactic, and return the PROPER response for the RR (Resource Record) -- Doesn't Exist.

    For those who don't/didn't have access to these/those DNS providers, or a Local DNS. It is a simple matter of adding an additional entry to the localhost file [cite needed]. Which fortunately, is available on every Network Enabled computer. It's part of the arpa standard. Generally speaking; it's as simple as adding the offending IP address to the file. Problem solved. There are also trickier implementations that can be employed. But, for the sake of this review, it's enough to say; simply add the IP.

    Best wishes.

    --Chris

    ¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

      while this will prevent you from accidentally sending confidential data to that Provider, you won't get back NXDOMAIN (which might be needed, depending on your application)
        True, if only implemented in it's simplest form, eg; simply adding the IP to the localhost file, and in the absence of local DNS. But, with the presence of local DNS, or the inclusion of a HOSTS file. Getting/Returning the correct response is fairly trivial.

        --Chris

        ¡λɐp ʇɑəɹ⅁ ɐ əʌɐɥ puɐ ʻꜱdləɥ ꜱᴉɥʇ ədoH

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: modulereview [id://293188]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others browsing the Monastery: (5)
As of 2024-03-28 17:28 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found