Chapter 7: Global FQDN configuration
You can use a single for all services or multiple FQDNs for each service. If you are using multiple
FQDNs, you require an external interface on the reverse proxy for each FQDN and separate
certificates for each FQDN.
In a single FQDN environment, remote clients and endpoints that participate in conferences interact
with multiple components through HTTPS. To eliminate the need for multiple external public IPs,
FQDNs, and certificates, the URL rewriting method is used. Using this method, clients and
endpoints can access conferences using a single FQDN and a single IP address through port 443.
DNS configuration
• For a single FQDN deployment, configure DNS as follows:
- For external DNS configuration, have a single FQDN record, for example,
webservices.company.com
, that points to the reverse proxy or load balancer interface
for external traffic.
- For internal DNS configuration, have a single FQDN record, for example,
webservices.company.com
, that points to the reverse proxy or load balancer interface
for internal traffic.
• For a multiple FQDNs deployment, configure DNS as follows:
- For external DNS configuration, each FQDN points to the external load balancer interface.
- For internal DNS configuration, each FQDN points to the individual server components.
Related links
Required FQDNs and certificates
Configuring the front-end FQDN
Procedure
1. Log in to the Avaya Aura
®
Web Gateway administration portal.
2. Navigate to
External Access
>
HTTP Reverse Proxy
.
3. Configure the following settings:
October 2018
Deploying the Avaya Aura
®
Web Gateway
96
