For Private Edge deployments, you need to deploy an Access Tier and register a domain that your organization owns and manages. You can then publish services using your registered domain(s).

Setup:

As in the diagram above, a user needs to access a web server located inside a private network. The private address of the this server is ngnix.bnn.local, and an Access Tier is deployed in that private network.

The user will access this resource at nginx.banyan.com. *.banyan.com is a Banyan registered domain with a public wildcard DNS record that resolves to the address of an Access Tier owned by the org.

Steps:

1. The user makes a request for the published web service (at nginx.banyan.com).

2. Since nginx.banyan.com is a published service on a registered domain, a public DNS server resolves the query and returns the public IP address of the org's Access Tier (in this case, 35.35.8.9).

3. The request from the user flows over the internet to reaches the Access Tier.

4. The Access Tier, located in the DMZ of the private network, queries its DNS server for the address of the specified backend (nginx.bnn.local) of the published service.

5. The private DNS server returns the private IP address (10.0.1.2) of the published service's specified backend.

6. The Access Tier reverse proxies the connection, granting the client access to the internal web server after validating user and device trust.