Hi Pankaj:
Basically for the Maximo Application Suite there are lots of "external" services and URLs both at the Suite and the applications level (such as Manage) that will need to be resolvable via DNS. They can seen as the "Routes" associated to the respective projects in OpenShift.
Given the sheer number of them we typically recommend setting up wildcard DNS records. Which makes administration and maintenance easier. Highly secure organizations may not like wildcard DNS records so in these cases "individual" records may need to be setup instead.
Also we typically use CNAME (aliases) in DNS to avoid repeating the same IP address in several records which also makes future maintenance easier (as the IP needs to be changed only in one place and all CNAME(s) will follow). Most of these "external" records will point to the "ingress" IP address or load balancer front end for cloud deployments.
Hope the above helps.
Thanks,
------------------------------
Julio Perera
Senior Maximo Technical Consultant
Interloc Solutions Inc., US.
------------------------------
Original Message:
Sent: Thu May 01, 2025 06:04 PM
From: Pankaj Bhide
Subject: Requirements for the new DNSs for MAS 9
Hello,
Our application service provider requested us to create a new set of the DNS records that include the following:
maxinst.manage.maximo-mas.<org home>
auth.maximo-mas.<org home>
Can you help me to understand why the above 2 new DNS records are required and what role do they in functioning of MAS and/or Manage?
Thanks
------------------------------
Pankaj Bhide
------------------------------