You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While preparing the installation, we specified a custom domain for our MAS instance. The domain is different from the Openshift's one.
During the MAS install, the OCP hostname is defined as apps.65e73b7612697b001299b3e7.cloud.techzone.ibm.com and this value is used to create the DNS CNAME records.
However, this configuration leads to dns_probe_finished_nxdomain.
To make the DNS work, I had to change the target host as router-default.apps.65e73b7612697b001299b3e7.cloud.techzone.ibm.com.
Attached, the YAML from the suite-dns task. suite-dns.log
The text was updated successfully, but these errors were encountered:
While preparing the installation, we specified a custom domain for our MAS instance. The domain is different from the Openshift's one.
During the MAS install, the OCP hostname is defined as
apps.65e73b7612697b001299b3e7.cloud.techzone.ibm.com
and this value is used to create the DNS CNAME records.However, this configuration leads to
dns_probe_finished_nxdomain
.To make the DNS work, I had to change the target host as
router-default.apps.65e73b7612697b001299b3e7.cloud.techzone.ibm.com
.Attached, the YAML from the suite-dns task.
suite-dns.log
The text was updated successfully, but these errors were encountered: