LBL DNS & Proxy Manager is the new and innovative product that allows you to dynamically set the name and address associations on the DNS, constantly verifying the reachability and operation of the application services.
LBL DNS & Proxy Manager allows you to constantly keep up-to-date multiple DNS nodes so that you always have the most up-to-date image of the network status and associated services.
LBL DNSManager makes it possible to create highly reliable infrastructures, Business Continuity and Disaster Recovery in a simple and effective way.
LBL DNSManager is also the right complement to LBL ADC Enterprise HA being able to manage different addresses in RoundRobin in a dynamic way presenting to the clients the actual availability of routing. This solution is a valid alternative where the use of Firewall with features of RoundRobin is not foreseen.
LBL DNSManager is released to cooperate with DNS BIND *** (https://www.isc.org/) and MS DNS *** which provide DNS services.
LBL DNSManager finds innumerable applications in the infrastructural field. Among these, the scenario of Disaster Recovery is undoubtedly the most representative. Among the many operations that must be performed to achieve the movement of services from one site to another, surely the adaptation of the pair name and addresses is among the most critical. LBL DNSManager manages this phase in complete autonomy, avoiding both human errors and errors generated by possible negative client cache (negative-cache prevention).
LBL DNSManager constantly verifying the availability of applications on the indicated sites is able to set the DNS automatically when changes occur. For the sole purpose of an example below, a scenario with two sites where in case of need the “secondary” site must be made available to clients when the application services are activated and ready for delivery.
The initial state provides two DNS, one per site. In the image beside LBL DNSManager detects the activity in the main site. Both DNS to a dnslookup will respond with the address where the availability of service delivery was detected.
The LBL DNSManager instances, both on the main site and on the secondary site, will continue to constantly check the activity of the application services until a change occurs. At the failure of the main site LBL DNSManager noting that the status change occurred will perform an update of the zones and related namespace of the DNS.
This situation persists until the moment when one of the two addresses and related applications will be active again. At that time LBL DNSManager detecting the activity and then a further change of status will dynamically modify the zones of its DNS by associating the new address. To a dnslookup the answer will be modified with the new address without any intervention.