--- title: "Configuring a domain with a single next-hop IP address using the CLI" slug: "configuring-a-domain-with-a-single-next-hop-ip-address-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-a-single-next-hop-ip-address-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 a single next-hop IP address using the CLI This procedure describes how to use the Email Security - Server appliance CLI to configure a domain with a single next-hop IP address. If you do not specify a TLS policy, the value `none` is used by default. If you specify a TLS policy (`opportunistic`, `mandatory`, or `verify`), you can also configure the MTA to use DNS MX record translation on the next-hop IP address. ### Prerequisites - An established connection between the Email Security - Server appliance and the Internet. - You are logged in to the Email Security - Server appliance CLI as an Admin or Operator. **To configure a domain with a single next-hop IP address:** 1. Go to CLI configuration mode. ``` hostname > enable hostname # configure terminal ``` 2. Specify the domain and one next-hop IP address. By default, the MTA TLS delivery mode is `none`. By default, MTA use of DNS MX record translation on the next-hop IP addresses is `false` (disabled). If you explicitly configure the delivery mode, you can enable the `mx` option. The following example configures the mydomain1.com domain with a single next-hop IP address and uses the default MTA TLS delivery setting (`none`): ``` hostname (config) # email-analysis domain mydomain1.com next-hop 172.17.74.10 ``` The following example configures the mydomain2.com domain with a single next-hop IP address and sets the default next-hop MTA TLS mode to `mandatory`. ``` hostname (config) # email-analysis domain mydomain2.com next-hop 172.17.74.20 tls-policy mandatory ``` The following example configures the mydomain3.com domain with a single next-hop IP address and sets the next-hop MTA TLS mode to `verify`. The MTA is configured to use DNS MX record translation on the next-hop IP address. ``` hostname (config) # email-analysis domain mydomain3.com next-hop 172.17.74.30 tls-policy verify mx true ``` 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 mydomain2.com subdomain-relay enable ``` > [!NOTE] > Note > > A domain and all subdomains created for it must point to the same next-hop IP address. 4. Verify your changes. ``` hostname (config) # show email-analysis Email-Analysis:  enabled                      yes    .    .    .  Domain(s):      domain: mydomain1.com          next hop mta: 172.17.74.10          MX Enable: false          TLS mode: none   Block Notice Enable: true   Subdomain Relay Enable: false      domain: mydomain2.com          next hop mta: 172.17.74.20          MX Enable: false          TLS mode: mandatory   Block Notice Enable: true   Subdomain Relay Enable: true      domain: mydomain3.com          next hop mta: 172.17.74.30          MX Enable: true          TLS mode: verify   Block Notice Enable: true   Subdomain Relay Enable: false ``` 5. Save your changes. ``` hostname (config) # write memory ```