×
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.
The problem with using the DNS server on IBM i is that the bind level is normally way behind. Even though IBM patches it to fix various CVE's they rarely raise the bind level, except at a new release level. Therefore you fail the audits, even from IBM audits.
A trick is to fudge the stream file (/QIBM/UserData/OS400/DNS/ATTREXT) to say it's at a higher bind level but I dislike lying to the auditors. Trust, when broken, is hard to regain.
We had to remove DNS from our DMZ lpars. Sad to lose tools like NSLOOKUP and stuff when that happened.
Two RFE's opened.
One to keep bind level current.
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=132234
One to unbind tools like NSLOOKUP from DNS (Declined).
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=99010
In the first one they claim they have a higher bind level with various PTF's for 6.1 to 7.3. Too bad it's not out for 7.4 as /QIBM/UserData/OS400/DNS/ATTREXT says to beware of velociraptors when out on a hike.
Rob Berendt
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.
midrange.com
