Add an FQDN

In the main menu, select Global Balancing and Manage FQDNs.

Click the Add FQDN button.

Enter an FQDN name, for example www.example.com in the New FQDN textbox.

Note: As of LoadMaster version 7.2.60.1, underscores are supported in this field.

Note: In LoadMaster firmware version 7.2.54.1 and earlier, the maximum number of possible FQDNs allowed is 256. For LoadMaster firmware version 7.2.55 or above, the number of possible FQDNs is limited by the size of the RAM available.

Note: The FQDN can be a maximum of 63 characters long. Otherwise, a pop-up message appears that says "FQDN must be 63 characters or less".

Note: Wildcards are supported here, for example *.example.com matches anything with .example.com ending.

Click the Add FQDN button.

Click OK on the message that appears.

Select the relevant load balancing algorithm from the Selection Criteria drop-down list.

If the Selection Criteria is set to Location Based, you can specify whether or not to allow Fail Over.

Select the relevant options for the Public Requests and Private Requests drop-down lists.

Note: When the Fail Over option is enabled, if a request comes from a specific region and the target is down, the connection will fail over and be answered with the next level in the hierarchy. For example, if the Selection Criteria is Location Based - the country comes first in the hierarchy, then continent. If this is not available, the connection is answered by the nearest (by proximity) target. If this is not possible, the target with the lowest requests is picked. The Fail Over setting affects all targets.

The Isolate Public/Private Sites setting has been enhanced as of version 7.1-30. The checkbox has been migrated to two separate dropdown menus to allow more granular control of DNS responses. Existing behavior has been preserved and is migrated from your current setting, ensuring that no change in DNS responses is experienced. These new settings allow administrators finer control of DNS responses to configured FQDNs. Administrators may selectively respond with public or private sites based on whether the client is from a public or private IP. For example, administrators may wish to allow only private clients to be sent to private sites.


Setting	Value	Client Type	Site Types Allowed
Public Requests	Public Only Prefer Public Prefer Private All Sites	Public Public Public Public	Public Public, Private if no public Private, Public if no private Private and Public
Private Requests	Private Only Prefer Private Prefer Public All Sites	Private Private Private Private	Private Private, Public if no private Public, Private if no public Private and Public

The following table outlines settings and their configurable values:

Enable/disable the ECS Public/Private Request Checking check box, as needed. When disabled, the device uses the client request’s source IP address to determine if the request is public or private. When enabled, the device uses the EDNS Client Subnet (ECS) value instead (if one is received) to determine if the request is public or private. This option becomes inactive in either of the following conditions:

The EDNS Client Subnet (ECS) option (in Global Balancing > Miscellaneous Params) is disabled.

The Public Requests and Private Requests values are both set to All Sites.

The ECS Public/Private Request Checking was added to the modify FQDN screen in LoadMaster firmware version 7.2.58.

The following table summarizes the behavior depending on the configuration:


EDNS Client Subnet (ECS) setting under Miscellaneous Params	Public/Private settings	ECS Public/Private Request Checking - Disabled	ECS Public/Private Request Checking - Enabled
Disabled / Off	Any	Public/private check is based on the source IP address	Public/private check is based on the source IP address as ECS for GEO is disabled
Enabled / On	If either option (Public Requests or Private Requests) is not set to All Sites	Public/private check is based on the source IP address	Public/private check is based on the ECS IP address
Enabled / On	If both Public Requests and Private Requests are set to All Sites	Public/private check is based on the ECS IP address - option is greyed out	Public/private check is based on the ECS IP address - option is greyed out

A Failure Delay (minutes) can be set if needed. If a Failure Delay is set, another option called Site Recovery Mode becomes available. Refer to the Enabling Fail Over section for further information on these options.

Note: Following a completely failed health check, the GEO LoadMaster waits for the specified number of minutes before taking the site out of rotation.

Enable/disable the Enable Local Settings check box, as needed. If enabled, configure the TTL and Stickiness options.

Enable or disable Unanimous Cluster Health Checks. If this option is enabled, if any IP addresses fail health checking – the other FQDN IP addresses in the same cluster is forced down. For further information, please refer to the Scheduling Methods section.

Enter the IP address of the domain in the IP address text box.

Note: We do not recommend downgrading the LoadMaster firmware version to a previous version where the endpoint limit of IP addresses per FQDN is smaller than the number of IP addresses in your configured FQDNs.

Note: The entry limit was increased to 256 IP addresses in LoadMaster firmware version 7.2.57. If you attempt to add more than this, you get an error message saying Limit of 256 IP Addresses has been reached for the FQDN. It is recommended that the LoadMaster should have sufficient memory space (minimum 8GB of RAM) to configure the maximum of 256 IP addresses per FQDN.

Note: In LoadMaster firmware versions prior to 7.2.57, there is an entry limit of 64 IP addresses per FQDN.

If needed, select the Cluster name.

Click Add Address.

Select the type of health checking to be performed from the Checker drop-down list. For further information regarding health checking options, refer to the FQDN Health Check Options section.

Select the Additional Records type to configure records for a specific FQDN. You can add, modify, or delete additional TXT, CNAME, and MX records to an FQDN. For more information and instructions, refer to the Additional Records section.

Note: Underscores are supported in the Data field for each of the record types.

Feature Description GEO

Add an FQDN

Table of Contents

Add an FQDN