In the XC platform, configuring a DNS Load Balancer requires users to navigate multiple screens. Initially, the user must create the load balancer, specifying pools, health checks, and geo-location sets. However, these configuration objects must first be set up on a separate screen before they can be incorporated into the LB. Once the DNS Zone is created, the pre-configured LB object from previous steps is linked under Resource Record Sets. This fragmented process creates friction and contrasts with the configuration flow of an HTTP Load Balancer.

In the case of an HTTP LB, all configuration steps are presented in a single form, allowing users to progress sequentially through options that cover most, if not all, necessary settings within one interface. This unified approach streamlines the user experience and eliminates the need to configure elements outside the LB setup. While some exceptions exist, such as service policies, they can still be managed under Common Security Controls within the HTTP LB configuration screen. Given this more efficient approach, M&T Bank is requesting a similar streamlined workflow for DNS LB configuration