Using IBM MQ Appliance v9.1, if DNS reverse lookup is enabled and the DNS servers become unreachable, an appliance reload may occur leaving queue managers in a partitioned state. Local fix Disable the Reverse DNS lookup, 10/11/2018 · You can disable this reverse DNS lookup using ALTER QMGR REVDNS(DISABLED). If you do this you need to change your CHLAUTH definitions to.
11/10/2015 · To change this default to prevent DNS lookups from taking place, use the installation property and value: enableReverseDNSLookups=false This property controls the behaviour when put in the FTE/MFT system’s installation property file.
4/17/2021 · If the REVDNS attribute is not enabled, DNS host names are not reverse looked-up for the IP addresses of inbound channels. For more information about the REVDNS attribute, see ALTER QMGR. Note that APAR IC96408 introduced reverse DNS hostname lookup for previous versions of IBM WebSphere MQ for the purpose, 10/26/2019 · With DNS it fails with ‘host not available’, 2538. Doing a bit of reading around it sounds like the DNS lookup / reverse DNS lookup may not be working correctly in windows 10 and when I did a client trace it looked like it was confirming a failure in the DNS lookup . RSESS:000001 xcsIsEnvironment[AMQ_NO_IPV6] = FALSE, 6/12/2019 · This might indicate a problem with the DNS configuration. ACTION: Ensure that DNS is correctly configured on the local system. If the address was an IP address then the slow operation was a reverse DNS lookup . Some DNS configurations are not capable of reverse DNS lookups and some IP addresses have no valid reverse DNS entries.
10/16/2019 · If the problem persists, consider disabling reverse DNS lookups until the issue with the DNS can be resolved. Have the receiving side disable reverse DNS lookup, and also disable …
