Apex Domains - DNS Managed Outside Barracuda

You must do the following for an Apex Domains if your DNS records are not configured through WAF-as-a-Service.

Notes:

An apex domain (i.e. barracuda.com) can only ever point to a single application.
If you do not have a fully qualified domain name (FQDN), you must change the configuration of your webserver (in WordPress, for example), to use an FQDN (www.example.com) instead of the apex domain (example.com).

On the Applications page, click the link for the target application.
On the Endpoints page, if they do not already exist, create both your:
- apex domain
- fully qualified domain name (FQDN)
Review any existing redirects for the domain on the web server. If there is already a redirect rule for the apex domain, you must disable or delete that rule before continuing.
Navigate to the URL Access & Redirects page. If it is not already set, switch Enable URL Access & Redirects to On.
Add a new URL rule to redirect from your apex domain to another, non-apex domain.
Barracuda Networks recommends using this form of URL redirect rule, being sure to include the %s : https://www.example.com%s
Refer to this example for creating your URL redirect rule. Refer to URL Access and Redirects for more information.
Wait about five minutes for the URL rule to take effect.
Optionally test the configuration. For example, in Linux, in your /etc/hosts file, set your domain to point to 20.55.103.191.
Check that the redirect works as expected before continuing with the next step.
Return to the Endpoints page. Copy the CNAME value.
In your DNS management panel, set the CNAME of non-apex domains to the CNAME value you copied in the previous step. Set the A record for the apex domain to the following IP address: 20.55.103.191. Note that this IP address will be the same for all applications.