Answers: <p>The AWS support finally helped, it was kind of blurry between RH and Route53. So, the trick is to find your endpoint in the Hosting Zone managed by Openshift, in our case:</p>
  <pre><code>*.example-com.test.plvo.p1.openshiftapps.com 
  </code></pre>
  <p>Note the Elastic Load Balancer it's pointing to (the &quot;Value/Route traffic to&quot; column). Then go back to the Hosting Zone in question and add an A record as an alias to the same ELB in its respective region.</p>
  <ul>
  <li><strong>record name:</strong> example.com</li>
  <li><strong>record type:</strong> A</li>
  <li><strong>route traffic to:</strong> [x] Alias</li>
  <li>Alias to Application and Classic Load Balancer</li>
  <li>[region of your ROSA cluster]</li>
  <li>[dualstack.the-ID-of-your-ELB.elb.amazonaws.com.]</li>
  </ul>
  <p>After 60 secs it's already propagated.</p>
  <p>thanks AWS!</p>
  
Answers: CC BY-SA 4.0
Answers: 2022-05-10T11:15:21.450Z
Answers: 2022-05-10T11:15:21.450Z
Answers: ptrk
Body: <p>We have a ROSA (Openshift on AWS) cluster, working fine with all kinds of domains except one, which happens to be an apex of the Hosting Zone in our Route53. So, say, the domain is <code>example.com</code> and it's registered in AWS with the name servers - all well. I have created a CustomDomain in the Openshift cluster that works for all it's subdomains eg. <code>www.example.com</code>. This is thanks to a wildcard CNAME record that points all <code>*.example.com</code> queries to <code>zhfsrc.example-com.test.plvo.p1.openshiftapps.com</code> provided by the CustomDomain object:</p>
  <pre><code>apiVersion: managed.openshift.io/v1alpha1
  kind: CustomDomain
  metadata:
    
    name: example-com
  
  spec:
    certificate:
      name: example-com-tls
      namespace: example
    domain: example.com
    scope: External
  status:
    conditions:
  ...
      - lastProbeTime: '2022-04-13T16:11:33Z'
        lastTransitionTime: '2022-04-13T16:11:33Z'
        message: Custom Apps Domain (example.com) Is Ready
        reason: Ready
        status: 'True'
        type: Ready
    dnsRecord: '*.example-com.test.plvo.p1.openshiftapps.com.'
    endpoint: zhfsrc.example-com.test.plvo.p1.openshiftapps.com
    scope: ''
    state: Ready
  </code></pre>
  <p>Now, I am missing the A record and this breaks the deal. Restrictions found:</p>
  <ul>
  <li>the apex domain cannot be a CNAME</li>
  <li>the A record in Route53 cannot point to a CNAME</li>
  <li>there is (apparently) no resource the A record can be an alias for (tried the openshift LBs)</li>
  <li>CNAME flattening is not available in Route53</li>
  </ul>
  <p>I see this as a most basic use case - a domain registered via AWS pointing to an Openshift application, yet neither RH nor AWS support were able to help so far.</p>
  
Tags: <amazon-web-services><dns><openshift>
Title: Apex domain to point to an Openshift ROSA application
UserDisplayName: ptrk
ThreadText: # Apex domain to point to an Openshift ROSA application
  
  (Asked by: username_0 on 2022-05-09)
  
  We have a ROSA (Openshift on AWS) cluster, working fine with all kinds of domains except one, which happens to be an apex of the Hosting Zone in our Route53. So, say, the domain is `example.com` and it's registered in AWS with the name servers - all well. I have created a CustomDomain in the Openshift cluster that works for all it's subdomains eg. `www.example.com`. This is thanks to a wildcard CNAME record that points all `*.example.com` queries to `zhfsrc.example-com.test.plvo.p1.openshiftapps.com` provided by the CustomDomain object:
  
  ```
  apiVersion: managed.openshift.io/v1alpha1
  kind: CustomDomain
  metadata:
    
    name: example-com
  
  spec:
    certificate:
      name: example-com-tls
      namespace: example
    domain: example.com
    scope: External
  status:
    conditions:
  ...
      - lastProbeTime: '2022-04-13T16:11:33Z'
        lastTransitionTime: '2022-04-13T16:11:33Z'
        message: Custom Apps Domain (example.com) Is Ready
        reason: Ready
        status: 'True'
        type: Ready
    dnsRecord: '*.example-com.test.plvo.p1.openshiftapps.com.'
    endpoint: zhfsrc.example-com.test.plvo.p1.openshiftapps.com
    scope: ''
    state: Ready
  
  ```
  
  Now, I am missing the A record and this breaks the deal. Restrictions found:
  
  * the apex domain cannot be a CNAME
  * the A record in Route53 cannot point to a CNAME
  * there is (apparently) no resource the A record can be an alias for (tried the openshift LBs)
  * CNAME flattening is not available in Route53
  
  I see this as a most basic use case - a domain registered via AWS pointing to an Openshift application, yet neither RH nor AWS support were able to help so far.
  
  **Tags:** amazon-web-services, dns, openshift
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2022-05-10. Score: 0
  
  The AWS support finally helped, it was kind of blurry between RH and Route53. So, the trick is to find your endpoint in the Hosting Zone managed by Openshift, in our case:
  
  ```
  *.example-com.test.plvo.p1.openshiftapps.com 
  
  ```
  
  Note the Elastic Load Balancer it's pointing to (the "Value/Route traffic to" column). Then go back to the Hosting Zone in question and add an A record as an alias to the same ELB in its respective region.
  
  * **record name:** example.com
  * **record type:** A
  * **route traffic to:** [x] Alias
  * Alias to Application and Classic Load Balancer
  * [region of your ROSA cluster]
  * [dualstack.the-ID-of-your-ELB.elb.amazonaws.com.]
  
  After 60 secs it's already propagated.
  
  thanks AWS!
  
  
  ---
  
  