Skip to content

Commit bfc92dc

Browse files
Update README.md (#444)
Minor fixes to README
1 parent 65e805c commit bfc92dc

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/solutions/regional_private_lb/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
# | |_| | _ < / ___ | |___| |___| |___
55
# \___/|_| \_/_/ \_\____|_____|_____|
66
***
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.
88

99
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.
1010

@@ -22,7 +22,7 @@ In case of an AD-level failure or when a private load balancer is down, 'monit'
2222
* Source env-vars
2323
* `$ . env-vars`
2424

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).
2626

2727
### Files in the configuration
2828

0 commit comments

Comments
 (0)