Re: Querying level of DNS Bind -- MIDRANGE-L

Subject: Re: Querying level of DNS Bind
From: Rob Berendt <rob@xxxxxxxxx>
Date: Tue, 29 Mar 2016 11:27:40 -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/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Thank you. That was a big help.

From another lpar:

QSH
dig @208.87.180.5 version.bind txt chaos
;; ANSWER SECTION:
version.bind. 0 CH TXT "9.7.4-P1.V7R2M0"

/QIBM/UserData/OS400/DNS/ATTREXT
....+....1....+....2....+....3....+....4....
************Beginning of data**************
bind_version=9.7.4
bind_patch_level=P1
************End of Data********************

/QIBM/UserData/OS400/DNS/ATTRIBUTES
....+....1....+....2....+....3....+....4....+
************Beginning of data**************
V7R2M0
************End of Data********************

I'll have to ask the boss about changing this. I don't think that's going
to swing. Displaying the lower bind to the scanners allows them to
suggest a CVE and we can query PTF cover letters and/or APARs for that CVE
and make sure that we're covered.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

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.