mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
OSDOCS-14718
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
b5118c9254
commit
ce03ff375e
@@ -124,7 +124,8 @@ $ aws route53resolver list-resolver-endpoint-ip-addresses \
|
||||
|
||||
Use the following procedure to configure your DNS server to forward the necessary private hosted zones to your Amazon Route 53 Inbound Resolver.
|
||||
|
||||
ifdef::openshift-rosa-hcp[]
|
||||
//ifdef::openshift-rosa-hcp[]
|
||||
=== ROSA with HCP
|
||||
ROSA with HCP clusters require you to configure DNS forwarding for two private hosted zones:
|
||||
|
||||
* `<cluster-name>.hypershift.local`
|
||||
@@ -197,9 +198,10 @@ zone "rosa.<domain-prefix>.<unique-ID>.p3.openshiftapps.com" { <1>
|
||||
----
|
||||
<1> Replace `<domain-prefix>` with your cluster domain prefix and `<unique-ID>` with your unique ID collected above.
|
||||
<2> Replace with the IP addresses of your inbound resolver endpoints collected above, ensuring that following each IP address there is a `;`.
|
||||
endif::openshift-rosa-hcp[]
|
||||
//endif::openshift-rosa-hcp[]
|
||||
|
||||
ifdef::openshift-rosa[]
|
||||
=== ROSA Classic
|
||||
ROSA Classic clusters require you to configure DNS forwarding for one private hosted zones:
|
||||
|
||||
* `<domain-prefix>.<unique-ID>.p1.openshiftapps.com`
|
||||
|
||||
Reference in New Issue
Block a user