Core Components
Other than the GSLB itself, the other core components that enables the GSLB functionality are
Appliance Components
Like everything else on the loadbalancer.org appliance, the GSLB is built on and with open-source software. There are two core components that make up the GSLB, PowerDNS and Polaris. PowerDNS is an extremely robust and well-supported software project. Polaris is an open source project now principally maintained by Loadbalancer.org. There have not been any updates to the project by the original maintainer and the most recent updates have been provided by Loadbalancer.org
PowerDNS
PowerDNS is an open-source DNS server software designed to provide a robust, scalable, and versatile platform for routing internet traffic. It is widely used for its high performance, ease of management, and flexibility, supporting various back-ends such as BIND, MySQL, PostgreSQL, and Oracle. PowerDNS features a strong security model and is capable of handling a vast number of queries per second, making it suitable for deployment in high-traffic environments. It is also known for its advanced features like DNSSEC for securing DNS lookups and a versatile API for automation and integration with other tools and systems.
Polaris
The Polaris GSLB project provides an open-source Global Server Load Balancing solution that can be extended for high availability across data centres and beyond. Polaris enhances the capabilities of PowerDNS Authoritative Server with features such as load-balancing methods, customisable health monitors, dynamic server weighting. It supports running health checks against different IPs from the member IP allowing a single Health Tracker to serve multiple DNS resolvers. Its setup is designed to be elastic and asynchronous, providing non-blocking communication between its internal components.
Environment Components
DNS Infrastructure
The constituent parts of the GSLB on the appliance are concerned with DNS as the GSLB functions, primarily, using DNS. The appliance cannot take control of DNS requests and responses on its own though. The network needs to be configured to pass DNS requests for the appropriate subdomains to the GSLB on the load balancer appliances. Whilst it is not technically a core component of the GSLB, it is a key part of the process, and needs to be understood for a successful implementation.
On Operating Systems other than Windows you are able to configure clients to direct themselves to particular DNS servers for certain subdomains. If you don't have any Windows systems in your environment, you don't necessarily have to make changes to the DNS infrastructure. However, we have not come across an environment where modification of the internal DNS infrastructure (domain delegation) is not required.