## Is this a solution which can work with a control panel?¶

cPanel users may try ZeroConf.

## Is IP fail-over setup available on ADC?¶

Yes, it is. Please see High Availability for configuration instructions.

## Does Web ADC support IPs on different interfaces?¶

There should not be any problem with multiple Network Interface Cards (NICs), as long as Keepalived allows it.

## Does Web ADC handle data synchronization across backend nodes?¶

No. Data synchronization across backend nodes is not a responsibility of the ADC. Web ADC is responsible only for its own internal states. For backend nodes, you will need shared storage for files, and DB replication for databases. If DB High Availability is not required, you can set up multiple web nodes that talk to one DB server.

No. Web ADC is a layer 7 load balancer. Layer 4 is used for MySQL, therefore Web ADC can not route traffic at a per-query level and it cannot split read/write.

## Where should cache rules be defined: Web ADC, or the underlying web server(s)?¶

LSCache is available to use at the ADC level, however for most basic setups, we suggest enabling LSCache at the backend server level instead. If you do choose to enable LSCache at the ADC level, you must be careful not to introduce any inconsistencies with the backend.

## Does Web ADC support mod_security rules?¶

Yes. The ModSec engine in LiteSpeed Web ADC is similar to the one in our LiteSpeed Web Server.

www.domain.com load balances across five servers.
www.domain.com/blog loads from a separate IP. Host headers will need to be preserved as the IP only responds to requests for www.domain.com.