Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (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.


Status Submitted
Created by Guest
Created on Mar 20, 2026

Python ibmmq lib: Support retrieving CCDT from DNS TXT Records apart from File, HTTP, HTTPS

IBM® MQ clients can currently retrieve CCDT information from a local file, FTP, HTTP, and HTTPS. While functional, these approaches rely on static files or external hosting, which adds complexity in modern cloud and container environments.

We propose allowing MQ clients to retrieve CCDT information directly from DNS TXT records.

With this enhancement, a client would specify a DNS name (for example,
<qmgrName>.mq.ms.com) using an environment variable such as MQCCDTURL or a new variable like MQCCDTDNS. The MQ client library would resolve the DNS TXT records and use the returned data exactly as it does today when reading a CCDT from a file or URL.

Benefits

  • Eliminates the need to distribute or manage CCDT files

  • Enables dynamic, DNS‑based service discovery

  • Fits naturally with cloud, container, and hybrid deployments

  • Requires no application code changes

  • Behaves consistently with existing CCDT support

Summary

Adding DNS TXT record support as a CCDT source would provide a lightweight, modern alternative for MQ client configuration, improving flexibility and operational simplicity while remaining fully backward compatible.

Idea priority High