PureEngage On-Premises

We're deploying on‑premise Edge servers for a customer, placed behind a firewall (DMZ). Genesys' published firewall rules include several URLs with wildcard characters, but the customer's security team won't allow wildcards, and their firewall also can't ingest the JSON file containing the full IP ranges. Is there any reliable way to extract or identify the exact IP addresses behind those wildcard URLs so the firewall can be updated accurately?

You may be able to resolve some IP addresses using DNS tools such as nslookup or dig, but that result is only a point-in-time DNS resolution and must not be treated as the complete or supported allowlist. These services may use dynamic DNS, regional routing, CDN/load balancing, failover, and NAT/proxy layers. The supported approach is to follow the Genesys-published firewall domains and IP/CIDR ranges, or use a firewall/proxy solution that supports FQDN and wildcard allowlisting.