Skip to Main Content

This is an IBM Automation portal for Integration products. 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 (

Shape the future of IBM!

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Oct 20, 2023

/etc/hosts function in the MQ on Cloud offering

In some configurations, particularly when using MQ clusters, Queue Managers may need a DNS-type service to function.

This is the case, for example, when a partial repository is located outside a private network, and has no access to the corporate DNS service. The easy and practical solution in this case is to use the /etc/hosts file, and enter the correspondence between the hostnames to be reached and their IP addresses.

IBM's MQ on Cloud offering has a number of limitations (not always well detailed) that can generally be overcome.

One such limitation is the lack of access to the /etc/hosts file, as MQ on Cloud is container-based. It is possible to activate a DNS service on MQ Cloud, but the corresponding pricing disqualifies the MQonCloud offer.

This limitation prevents the integration of a Partial Repository located on MQ on Cloud with an MQ cluster located on a private network.

To solve this problem, IBM needs to provide MQ on Cloud with a function providing the same services as the /etc/hosts file.

Idea priority Urgent
  • Admin
    Marcus Kaye
    Feb 28, 2024

    Marcus and Phil spoke to Luc-Michel Demey - the issue here is for MQoC to map a private hostname to a public IP address.

    This means that MQoC will need to add functionality to support private DNS hostname resolution.

    Next steps: MQoC team will size this work.

  • Admin
    Marcus Kaye
    Feb 20, 2024

    The etc/hosts/ file is not able to be edited directly in a SaaS service so is not applicable here. However allowing customer to edit files within the OS like that in a SaaS service would be a security risk in a public cloud environment.

    There are alternatives provided by IBM Cloud - public DNS is supported by IBM Cloud VPE which is now supported in the Reserved Instance MQ on Cloud plan.