dns cache poisoning -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: dns cache poisoning
From: "Jim Franz" <franz400@xxxxxxxxxxxx>
Date: Wed, 9 Jul 2008 23:48:15 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Any indication the i has issues with the dns cache poisoning vulnerability?
The Cert reference mentions Bind 8 which is where V5R3 was at and guess we still are. IBM eserver listed as "unknown" as in no response (yet) from vendor.
http://www.kb.cert.org/vuls/id/800113

Bind 8 specifically in this link:
http://www.kb.cert.org/vuls/id/927905

Jim Franz

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: dns cache poisoning , ChadB
Re: dns cache poisoning , rob

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.