pageoneresults - 8:28 am on Apr 19, 2006 (gmt 0)

Are you aware that link redirects to another site and doesn't appear to have that list.

No, can you please explain? There are two links at the bottom of that page, one for 2006 February and one for 2006 March which lead to the actual blacklist. The other two go to the IRCache site which used to contain the blacklist.

I have a question--how do those of us, who know nothing about administring servers, determine if our clients, that are on OPEN DNS Servers, need to move to a new host when the host claims they don't have a problem?

At this point, I might pose that question to the creator of the tool at DNS Report. They do have a small forum over there where Scott (the Admin) will answer your questions pertaining to the report.

My understanding is that if the site your server is hosted on fails for Open DNS, that there may be some issues there for you to contend with and it is worth investigating even if you find out that the least that could happen is that the server would be used in a DDoS attack.

We have an ongoing, periodic survey that looks for DNS cache poisoners. A nameserver may be able to poison vulnerable DNS caches by returning bad (incorrect) referrals for important domains. If a local caching resolver trusts the bad referral, future queries for the affected domain are sent to the wrong nameserver, which may refuse to answer the queries or provide incorrect answers. DNS resolvers for Microsoft Windows NT, 2000, and 2003 are vulnerable to cache poisoning. Windows 2003 is not vulnerable by default, but may become vulnerable if the administrator unchecks the "prevent cache poisoning" option.