In the DNS Specifications, Bluemix Local has 3 wildcard redirects: bluemix.net, mybluemix.net, and custom.
A client is requesting to be able to replace the bluemix.net DNS by its own such mycompany.cloud.net
This client is asking because this is a blocking point due to their proxy policy.
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.
Thanks everyone for submitting this idea. This is still under consideration for Bluemix Local.
We will not be implementing this for Bluemix Dedicated. This feature is incompatible with both our strategic and technical direction going forward.
Is this similar to IDEA-I-23?
Lionel - what is the customer's proxy policy specifically? Why would they specifically want to block the bluemix.net entry but not the mybluemix.net entry? Why does the custom redirect not suffice?
Thanks Lionel. This is a known requirement and we have it prioritized in our backlog. We are working with our Cloud Foundry team to bring this requirement through open source in order to deliver on this. Thanks for adding your input.