Configuring a forwarding LB action
Configuring the forwarding mode
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter DNS LB action view. | loadbalance action action-name | N/A |
3. Configure the forwarding mode. | forward all | By default, the forwarding mode is to discard packets. |
Specifying a DNS server pool for guiding packet forwarding
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter DNS LB action view. | loadbalance action action-name | N/A |
3. Specify a DNS server pool for guiding packet forwarding. | dns-server-pool pool-name [ sticky sticky-name ] | By default, no DNS server pool is specified for guiding packet forwarding. |
Skipping the current transparent DNS proxy
Perform this task to skip the current transparent DNS proxy and match the next transparent DNS proxy or virtual server.
To skip the current transparent DNS proxy:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter DNS LB action view. | loadbalance action action-name | N/A |
3. Skip the current transparent DNS proxy. | skip current-dns-proxy | By default, the forwarding mode is to discard packets. |
Matching the next rule upon failure to find a DNS server
Perform this task to enable packets to match the next rule in an LB policy when no DNS servers are available for the current LB action.
To match the next rule upon failure to find a DNS server:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter DNS LB action view. | loadbalance action action-name | N/A |
3. Match the next rule upon failure to find a DNS server. | fallback-action continue | By default, the next rule is not matched (packets are dropped) when no DNS servers are available for an LB action. |