You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/solutions/regional_private_lb/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
# | |_| | _ < / ___ | |___| |___| |___
5
5
# \___/|_| \_/_/ \_\____|_____|_____|
6
6
***
7
-
This example configures a regionally highly-available private load balancer using custom DNS servers.
7
+
This example configures regionally highly-available private load balancers using custom DNS servers.
8
8
9
9
It creates a VCN with the required subnets and other components, and it creates two private load balancers in two availability domains with the same set of backend instances.
10
10
@@ -22,7 +22,7 @@ In case of an AD-level failure or when a private load balancer is down, 'monit'
22
22
* Source env-vars
23
23
*`$ . env-vars`
24
24
25
-
Once the environment is built, the DNS VMs will be able to query the DNS hostnames within the VCN. You can run 'nslookup <fqdn-of-the-app>' from any instance in the VCN (that uses default DHCP options) to verify this.
25
+
Once the environment is built, you can connect to the load-balanced application using the FQDN (ha_app_name.ha_app_domain) from any instance in the VCN (that uses default DHCP options or the DNS VMs as the customer DNS resolvers).
0 commit comments