Linking FortiGSLB to domain register

To leverage FortiGSLB's load balancing capabilities, you need to point your domain's name server to your FortiGSLB Cloud service. Configuring Objects on FortiGSLB

This section covers the following:

• General Procedures for directing your domain's name server to FortiGSLB

• Configuration Examples

  • Modifying your domain registration with AWS Route 53

  • Setting up a new FortiGSLB application with Network Solutions

General Procedures for directing your domain's name server to FortiGSLB

For those migrating a domain from another vendor to GSLB, it is crucial to configure the object on FortiGSLB before performing the steps on this page to avoid any temporary service interruptions. If you are setting up a brand new domain, the sequence of steps does not affect functionality.

We recommend performing the following optional steps prior to setting up your domain: Navigate to DNS Services > Zone within the FortiGSLB Cloud GUI. Ensure that the “Domain Name,” “Primary Server Name,” and “Primary Server Address matches the DNS Services > Zone one on your FortiGSLB Cloud. It's recommended to set the “Primary Server Address” to match the assigned DNS Server IP. These steps are recommended but not mandatory. If you skip these steps, FortiGSLB will use default values for the domain settings.

Set Name Servers and Glue Records via Web Host:

1. DiG from FortiGSLB Cloud to see your application's SOA records. Take note of your Name Severs and Glue Records.

2. Access your web host's settings.

3. Set the Name Servers and Glue Records using the SOA records directly provided by FortiGSLB.

   Note: Changes to name servers may take time to propagate globally. The name server (NS) is specified in the Start of Authority (SOA) record, while the glue records are the IP addresses linked to the NS records.

Configuration Examples

Typically, you can adjust your DNS records through your web host or the domain registrar from which you obtained your domain.

Here are procedures for AWS Route 53 and Network Solutions, both prominent domain registrars. However, keep in mind that other vendors like GoDaddy, Cloudflare, and local registrars may offer different processes.

Modifying your domain registration with AWS Route 53

Below is the procedure for users who have registered their domain names through AWS Route 53.

1. Sign in to the AWS Management Console.
2. Go to Registered domains and click your Domain Name. Route 53 will display details of the domain. Click on Manage DNS.
   
3. Go to Add or edit name servers on the domain general information page. Set the Name servers and Glue records as SOA records directly taken from FortiGSLB. Route 53 requires at least two name servers, so do not delete all other name servers.
   

   Note:Changes to Route 53 name servers may take time to propagate globally. The name server (NS) is specified in the Start of Authority (SOA) record, while the glue records are the IP addresses linked to the NS records.
   
   

   Your domain SOA records should look something like the following when you DiG from FortiGSLB directly.
   

4. If you enabled the DNSSEC for the domain, you can configure the DNSSEC by clicking Manage Keys. Select Key type and Algorithm, and paste the Public key without any spaces. Keys can be downloaded from the FortiGSLB zone configuration page.
   

   The following key file indicates that it is a key-signing key file and the algorithm is 5. Usually there will be two parts of the key, separated by a space. When you paste the key into Route 53 Manage DNSSEC keys, make sure to remove the space.

   

Setting up a new FortiGSLB application with Network Solutions

1. To begin, prepare the domain within FortiGSLB. Navigate to DNS Services > Zone and configure the Zone service settings. Make sure you pay attention to the Domain Name, Primary Server Name, and Primary Server Address fields. We recommend setting the Primary Server Address to match the assigned DNS Server IP.
   
2. Register a domain from Network Solutions. Once completed, you should see the following window.
   
3. Click on Change Where Domain Points. In the Domain Name Pointing Options window, select the Domain Name Server (DNS) option and click Continue.
4. When configuring with Network Solutions, you need at least two name servers. Designate Name Server 1 as the primary server and Name Server 2 as the secondary. In the Specify Other Domain Name Servers section, enter the NS server for Name Server 1, which corresponds to the Primary Server Name and Domain Name from the FortiGSLB Zone page. If you have a backup server, input its NS info for Name Server 2. Otherwise, provide alternative information and proceed.
   
5. Under Create New Name Servers, input the IP address for Name Server 1 and input the backup server's IP address for Name Server 2. If you do not have a backup server, input the same IP as Name Server 1 and click Continue.
   
6. Double check the name server configuration and confirm the changes by clicking Apply Changes. It may take 24 - 48 hours for DNS changes take effect.
7. Click Return to Domain Details. After about 5 minutes, you will be able to DiG the A record for this domain from the public DNS server.