Kemp Support, how can we help?

The latest application delivery knowledge and expertise at your fingertips.

GEO Release Notes

GEO Version is a feature and bug fix update for the General Availability (GA) branch, made available on 27 March 2023. Please read the sections below before installing or upgrading to this release.

These notes list the fixes related directly to GEO product functionality. For a list of the new features, changes, and fixes in the base LMOS system on which GEO is running, please see the LoadMaster Release Notes for LMOS

Upgrade Notes

Please see the LoadMaster Release Notes for LMOS for a list of supported models for this release as well as for other upgrade notes, including how to validate the update image's digital signature.

New Features

GEO HTTP HEAD Site Health Checks

GEO site health checking has been expanded to include the HTTP HEAD method. This can be useful for many different application types. The following configuration options are supported:

  • Specify the name and content of a specific header to provide to the application.
  • Up to 4 custom headers can be defined per GEO Site.
  • The status of the last health check performed is reflected in the UI and log.
  • Return codes of 200-299, 301, 302, and 401 are interpreted to mean the server is healthy.

The following example shows how to configure an HTTP HEAD check to authenticate to the site using basic authentication via the Authorization header. The header value is “Basic”, followed by a space, followed by a base64-encoded string.

GEO System Information & Debug Page

A new Global Balancing > GEO System Info / Debug page provides the following status information to aid in troubleshooting DNS issues:

  • GEO Configuration
  • DNS Services
  • Partners & Clients
  • File System Stats
  • GEO IP DB version

In addition, new GEO Debug Options are provided at the bottom of the page:

  • Manually restart all GEO services.
  • Enable/disable partner syncing. Disabling it may be useful when debugging complex environments. While its disabled, the manual sync button still operates.
  • Manually sync GEO partners using verbose debug logging.
  • Retrieve status of all remote cluster Virtual Services using verbose debug logging.
  • Open logs (without having to go to the logging UI).
  • Enable debug logging for SSH connections.
  • Enable debug logging for DNS queries.

Most of these options should be used with caution and only to debug specific issues for a limited period of time. Debug logging, for example, can consume a significant amount of system resources while enabled.

Issues Resolved

LM-2252 GEO: Fixed an issue that caused a segmentation fault when a DNS Time Signature (TSIG) record is received. [Note: TSIG records are ignored by GEO.]
LM-1900 GEO: Fixed an issue wherein using the All Available selection criteria can cause the name resolution daemon (named) to consume additional resources and provide unexpected responses.
LM-1735 GEO: Fixed an issue where GEO is disabled but spurious logs and alerts appear warning about the failure of GEO processes.
LM-1723 GEO Partnering: There is a small window of time during a partner sync where concurrent changes on the partners may not be reflected on both systems. The only workaround is to repeat the modification.
LM-662 GEO: In previous releases, Cluster Checks can be selected even when there are no clusters present. This UI issue has been fixed.  

Existing Known Issues

LM-2034 GEO: Starting with, using the Real Server Load selection criteria may result in no traffic being processed. 
LM-1527 GEO Cluster Checks: GEO cluster checks against LoadMasters configured in Clustering mode do not work.


GEO Downgrade: When downgrading from a release that supports more than 64 IPs per FQDN to a release that only supports up to 64 IPs per FQDN, the GEO configuration may become corrupted if there is at least one FQDN in the configuration that contains more than 64 IP addresses. The corruption will likely be evidenced by errors in the UI/API when you list the FQDNs.

To avoid this issue entirely, reduce the number of IPs per FQDN to 64 or less for all FQDNs defined before you downgrade.

If you have already downgraded, you can switch back to the previous boot partition to go back to the newer release (which supports > 64 IPs per FQDN); you can then reduce the number of IPs as above and downgrade again.

If neither of these options is possible, please contact Kemp Support who will consult with engineering on a solution to your issues.      


GEO Cluster Status: When adding a Cluster that is unavailable (DOWN) to a Site, the Site may reflect the Cluster's status as available (UP) for a short time before changing to DOWN.  



GEO: Modifying an FQDN entry displays a spurious error on the system console, similar to the one shown below. The FQDN is modified properly.

<FQDN>:794 Uncaught ReferenceError: disp_addrr_elements is not defined

    at <FQDN>:794

(anonymous) @ <FQDN>:794



GEO: Cannot configure GEO into partnering mode unless there is at least one FQDN already defined.



GEO: No statistics (queries per second, etc.) are displayed for a site if the FQDN is configured to use the "All Available" Selection Criteria.


GEO: If you add a Zone Name to GEO after you have created working FQDNs, GEO may no longer respond to queries for one or more of the FQDNs after the Zone Name is added. The workaround is to remove and then re-add the FQDNs that are no longer working.


GEO: DNS TCP requests from unknown sources are not supported.


Was this article helpful?
0 out of 0 found this helpful