This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
We have a problem with the SOCKS configuration in Mainframe that dont allow the use of DNS on the FTP server destination and only allow the use of IP Address.
My concern here is that the network department setup rules on the SOCKS Server (the one we use on mainframe SOCKS configuration file) and generally they use DNS not IP Address for the FTP Server destinations but the mainframe side have the limitation that cant use DNS for the FTP Server destination they need to setup instead the IP Address and need to be specific not general and wide open IP Address.
Motivated to my previous explanation we need to worried if the IP address of the FTP Server destination change because the FTP client on the mainframe side will fail and not because the SOCKS configuration on Mainframe but because the rules that was setup on the SOCKS Server will not match anymore and therefore dont allow the FTP connection.
The Port is also a limitation that only alow the use of the Port 1080 and sometimes this is already restricted.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
We would like to see the enhancement include support for FQDN as described in
https://tools.ietf.org/html/rfc1928
Specifically Section 4. Requests ATYP=3, further described in Section 5. X'03'
the address field contains a fully-qualified domain name. The first
octet of the address field contains the number of octets of name that
follow, there is no terminating NUL octet.
Our issue with the present implementation in zOS is that only the IP Address can be configured in SOCKSCONFIGFILE. Our FTP client jobs have the FQDN coded (I presume for similar reasons to the original RFE request) and DNS resolution is performed before the lookup by address in the file so it can be forwarded on to the SOCKS server. We're attempting to isolate our internal DNS from external name resolution and therefore require the FQDN to be passed to the SOCKS5 server on the network edge for resolution and it's use in the proxy connection to external servers.