Using a Custom Domain Instead of IP Whitelisting

Some network teams prefer to allow access by domain name instead of by IP range. A Files.com Custom Domain lets you use your own hostname (for example, files.example.com) as the allow rule, instead of whitelisting the Files.com-owned IP block.

This is useful when your firewall or secure web gateway supports FQDN whitelisting and your policy prefers domain-based controls.

When This Approach Works

Use this approach when your network security tools support whitelist rules based on hostnames (FQDNs). It works well when you want users and client applications to connect through a single, consistent domain name. It also simplifies internal change management because it removes the need to maintain and update lists of IP address ranges.

Do not use this approach if your network environment allows whitelisting only by static IP addresses.

Plan Availability

Custom Domains are available on the Power and Enterprise plans.

What Changes (And What Does Not)

A Custom Domain now allows your users to also connect using the hostname.

A Custom Domain does not change that connections ultimately resolve to Files.com infrastructure. Your network must still allow the required Files.com service hostnames for the features you use.

If you operate in a default-deny model, start with the hostnames list in Hostnames Used by Files.com.

Setup Steps

Configure Your Custom Domain

• Follow Configuring Your Custom Domain.

Update Your Network Rules to Allow the Custom Domain

• In your firewall or secure web gateway, allow outbound access to your custom domain hostname.
• If supported, allow the exact hostname, not a broad wildcard.

Update Client Configurations

• Update bookmarks, integrations, and client apps to connect using the custom domain hostname.
• Keep the old connection settings until the new hostname is validated from all required networks.

Will This Disrupt Existing Connections?

It does not have to.

Roll this out gradually by moving users and integrations to the new hostname over time. Your Files.com site can still be accessed via your Files.com-provided subdomain.

If you use SSO, review your IdP settings for any domain-locked callback URLs. See Configuring Your Custom Domain.