Skip to content

[enterprise-4.14] Update installation-user-provisioned-validating-dns.adoc #65679

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bscott-rh merged 1 commit into from
Oct 3, 2023
Merged

[enterprise-4.14] Update installation-user-provisioned-validating-dns.adoc #65679

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions modules/installation-user-provisioned-validating-dns.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ $ dig +noall +answer @<nameserver_ip> api.<cluster_name>.<base_domain> <1>
.Example output
[source,terminal]
----
api.ocp4.example.com. 0 IN A 192.168.1.5
api.ocp4.example.com. 604800 IN A 192.168.1.5
----

.. Perform a lookup against the Kubernetes internal API record name. Check that the result points to the IP address of the API load balancer:
Expand All @@ -60,7 +60,7 @@ $ dig +noall +answer @<nameserver_ip> api-int.<cluster_name>.<base_domain>
.Example output
[source,terminal]
----
api-int.ocp4.example.com. 0 IN A 192.168.1.5
api-int.ocp4.example.com. 604800 IN A 192.168.1.5
----

.. Test an example `*.apps.<cluster_name>.<base_domain>` DNS wildcard lookup. All of the application wildcard lookups must resolve to the IP address of the application ingress load balancer:
Expand All @@ -73,7 +73,7 @@ $ dig +noall +answer @<nameserver_ip> random.apps.<cluster_name>.<base_domain>
.Example output
[source,terminal]
----
random.apps.ocp4.example.com. 0 IN A 192.168.1.5
random.apps.ocp4.example.com. 604800 IN A 192.168.1.5
----
+
[NOTE]
Expand All @@ -91,7 +91,7 @@ $ dig +noall +answer @<nameserver_ip> console-openshift-console.apps.<cluster_na
.Example output
[source,terminal]
----
console-openshift-console.apps.ocp4.example.com. 0 IN A 192.168.1.5
console-openshift-console.apps.ocp4.example.com. 604800 IN A 192.168.1.5
----

.. Run a lookup against the bootstrap DNS record name. Check that the result points to the IP address of the bootstrap node:
Expand All @@ -104,7 +104,7 @@ $ dig +noall +answer @<nameserver_ip> bootstrap.<cluster_name>.<base_domain>
.Example output
[source,terminal]
----
bootstrap.ocp4.example.com. 0 IN A 192.168.1.96
bootstrap.ocp4.example.com. 604800 IN A 192.168.1.96
----

.. Use this method to perform lookups against the DNS record names for the control plane and compute nodes. Check that the results correspond to the IP addresses of each node.
Expand All @@ -121,8 +121,8 @@ $ dig +noall +answer @<nameserver_ip> -x 192.168.1.5
.Example output
[source,terminal]
----
5.1.168.192.in-addr.arpa. 0 IN PTR api-int.ocp4.example.com. <1>
5.1.168.192.in-addr.arpa. 0 IN PTR api.ocp4.example.com. <2>
5.1.168.192.in-addr.arpa. 604800 IN PTR api-int.ocp4.example.com. <1>
5.1.168.192.in-addr.arpa. 604800 IN PTR api.ocp4.example.com. <2>
----
+
<1> Provides the record name for the Kubernetes internal API.
Expand All @@ -143,7 +143,7 @@ $ dig +noall +answer @<nameserver_ip> -x 192.168.1.96
.Example output
[source,terminal]
----
96.1.168.192.in-addr.arpa. 0 IN PTR bootstrap.ocp4.example.com.
96.1.168.192.in-addr.arpa. 604800 IN PTR bootstrap.ocp4.example.com.
----

.. Use this method to perform reverse lookups against the IP addresses for the control plane and compute nodes. Check that the results correspond to the DNS record names of each node.