--- title: "Configuring a domain with multiple next-hop IP addresses using the CLI" slug: "configuring-a-domain-with-multiple-next-hop-ip-addresses-using-the-cli" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-08-24T19:53:02Z published: 2026-08-24T19:53:02Z canonical: "docs.trellix.com/configuring-a-domain-with-multiple-next-hop-ip-addresses-using-the-cli" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring a domain with multiple next-hop IP addresses using the CLI This procedure describes how to use the Email Security - Server appliance CLI to configure a single domain with multiple next-hop IP addresses. If you do not specify a TLS policy, the value `none` is used by default. If you specify a TLS policy (`opportunistic` or `mandatory`), you can also configure the MTA to use DNS MX record translation on the next-hop IP address. ### Restrictions - TLS delivery mode can be set to `none`, `opportunistic`, or `mandatory`. The `verify` delivery mode does not support domains that forward to multiple MTA hosts. - A domain can support up to five next-hop addresses. - The total of the weighting values assigned to the next-hop entries must total 100. ### Prerequisites - An established connection between the appliance and the Internet. - You are logged in to the appliance CLI as an Admin or Operator. **To configure a single domain with multiple next-hop IP addresses:** 1. Go to CLI configuration mode. ``` hostname > enable hostname # configure terminal ``` 2. Specify the domain, up to five weighted next-hop IP addresses, and an optional TLS delivery mode. ``` hostname (config) # email-analysis domain mydomain4.com next-hop 172.16.244.10 weight 40 next-hop 172.16.244.20 weight 20 next-hop 172.16.244.30 weight 20 next-hop 172.16.244.40 weight 20 tls-policy mandatory Multiple next hops(4) configured for domain mydomain4.com ``` By default, the MTA TLS delivery mode is `none`. For a domain with multiple next-hop addresses, the valid delivery modes are `none`, `opportunistic`, and `mandatory` only. By default, MTA use of DNS MX record translation on the next-hop IP addresses is `false` (disabled). If you explicitly configure TLS delivery mode, you can enable the `mx` option. 3. If you want to enable email for all subdomains of a specified domain, use the **email-analysis domain subdomain-relay enable** command. ``` hostname (config) # email-analysis domain mydomain4.com subdomain-relay enable ``` 4. Verify your changes. ``` hostname (config) # show email-analysis Email-Analysis:    enabled                    yes      .      .      .  Domain(s):    domain: mydomain4.com        next hop mta: 172.16.244.10            weight: 40        next hop mta: 172.16.244.20            weight: 20        next hop mta: 172.16.244.30            weight: 20        next hop mta: 172.16.244.40            weight: 20        TLS mode: mandatory Block Notice Enable: true Subdomain Relay Enable: true ``` 5. Save your changes. ``` hostname (config) # write memory ```