Merge pull request #65648 from BabbarPB08/patch-4

Update installation-user-provisioned-validating-dns.adoc

Author: bscott-rh

modules/installation-user-provisioned-validating-dns.adoc

@@ -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:
@@ -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:
@@ -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]
@@ -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:
@@ -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.
@@ -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.
@@ -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.