openshift_master_default_subdomain doesn't resolve internally - AWS
tui-tomds opened this issue · 1 comments
Deployed a cluster using the 3.9 scripts on AWS. But the openshift_master_default_subdomain doesn't resolve from the nodes itself due to the fact that there is no DNS entry in the private AWS Route53 zone. Route 53 doesn't forwards requests to a public DNS resolver when the domain matched the private zone.
If there's a matching private hosted zone but there's no record that matches the domain name and type in the request, Amazon EC2 doesn't forward the request to a public DNS resolver. Instead, it returns NXDOMAIN (non-existent domain) to the client.
Reference: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html
I fixed it by adding the *.app. DNS record in the private zone that points to the public facing infra ELB. But it might be an extra option to also add an internal infra ELB itself.