Dedicated IP addresses are exclusive to your Files.com site. They let a counterparty allow a small set of addresses instead of the Files.com owned range, and let a domain present its FTPS certificate or SFTP host keys before a client identifies the site.

Files.com automatically provisions two dedicated addresses for a Primary Custom Domain. Additional Custom Domains can receive their own one- or two-address allocations. Custom Domains and dedicated addresses are available on the Power and Enterprise plans. Files.com does not offer IPv6 dedicated addresses.

These addresses cover connections to the domain and supported outbound connections. They do not replace the storage and feature hostname requirements for web and API transfers.

Address Allocation

Setting up a Primary Custom Domain allocates its pair automatically. Creating an additional domain or attaching its certificate does not allocate addresses. A Site Administrator selects Add Dedicated IPs in the Custom Domains table for that domain, chooses 1 IP Address or 2 IP Addresses, then submits. This action is available for any destination while the domain has no dedicated addresses.

Allocation is a one-time choice for each additional domain. After allocation, the action disappears and the Dedicated IP Addresses for This Domain column shows the assigned addresses. Copy the domain's updated CNAME target from DNS Configuration in the SSL Certificates settings and update the record at your DNS provider. Update any firewall allowlists that need to reach the new addresses.

Dedicated-IP allowances are pooled across a Parent Site and all its Child Sites. Each allocated set counts toward that allowance, whether it contains one or two addresses. The message Cannot allocate another set of dedicated IP addresses for this plan. means the pool is exhausted; contact Files.com for additional capacity. For an allocation-capacity error that asks you to try again in an hour or two, contact support if it persists.

You can retrieve allocated addresses with the CLI. For outbound Remote Server allowlists, use the Outbound IP Addresses column rather than the full allocation column. Only addresses eligible for outbound use appear there. The Remote Server's details also show the selected domain's outbound addresses under Connection Routing. Give every outbound address shown to the counterparty.

Subdomain Addresses and Certificates

Your certificate-management choice determines whether the Files.com subdomain also uses the Primary Custom Domain's dedicated addresses.

Dedicated IP Addresses With Files.com-Provided SSL Certificates

With a Files.com-managed certificate for the Primary Custom Domain, inbound connections to [subdomain].files.com also use the site's dedicated addresses. The Primary Custom Domain's CNAME points at that Files.com subdomain.

Dedicated IP Addresses With Your Own SSL Certificates

With your own certificate, the Primary Custom Domain uses dedicated addresses, while [subdomain].files.com continues to use the general Files.com address pool. Connections through the Files.com subdomain still receive a Files.com certificate.

Retaining the Primary IPs of Your Subdomain

Providing your own certificate lets established connections through [subdomain].files.com keep using the general pool while the new domain uses dedicated addresses. This can avoid requiring partners to change their existing connection information just to support a rebrand. Upload and activate your certificate, configure the Custom Domain and its DNS records, and maintain certificate renewal to avoid interruptions.

Dedicated IP Addresses for Outbound Connections from Files.com

Supported Remote Servers can use the site's default dedicated addresses, a selected Custom Domain's eligible outbound addresses, or the general pool. The choice applies to operations using dedicated-IP routing for Sync and Remote Server Mount. Selecting a domain lets each connection use the addresses its counterparty allows; Workspace availability controls which domains the connection can select.

Custom SMTP uses the general pool by default. A site with default dedicated addresses can enable their use through the Files.com API.

Webhook notifications, Event Channel Webhook targets, and AS2 trading partners use the general pool unless dedicated-IP routing is enabled for that webhook, target, or partner. They use the site's default dedicated addresses, without selecting an additional Custom Domain's addresses.

Direct SIEM log streaming automatically uses the site's default dedicated addresses when available and otherwise uses the general pool. It has no option to select the general pool or another domain's addresses. LDAP connections use the general pool.

For connections with a routing choice, retain the shared pool unless a counterparty requires fixed source addresses. Configure the receiving firewall for the choice actually used; an inbound domain allocation alone does not establish the source addresses for every outbound feature.

Static IP Addresses

Dedicated addresses act as effectively static addresses. Files.com works to keep them unchanged and provides advance notice of changes when possible. Removing a domain or changing the site's primary region affects that assignment. Continue using hostnames in clients so DNS can direct connections to the active addresses.

Regional Changes

The site's root-folder region determines the region of its Custom Domain and dedicated addresses. Changing that region assigns new addresses in the new region and releases the old ones. The new addresses are assigned during the change and are not available beforehand.

Plan a maintenance window for a root-region change with a Custom Domain. Certificate and DNS changes can interrupt access through the domain for approximately 15 minutes. A low DNS TTL shortens the time clients retain the old destination, but using a hostname alone does not guarantee an uninterrupted transition.

Notify partners of the planned change and arrange how to give them the new addresses for their allowlists. Test their connections after the change. Folder migration keeps native files accessible during storage relocation; that storage behavior does not remove the separate endpoint change.

Releasing IP Addresses

Removing the Primary Custom Domain takes its addresses out of active use. They are released after five days. Restoring the Custom Domain setting and correct DNS configuration within that period retains the addresses. Complete a domain replacement within the same five-day window to avoid releasing them.

Enabling proxying on the Primary Custom Domain's DNS records also releases its addresses because Files.com can no longer confirm that traffic reaches the site directly. Custom Domain DNS Records explains the DNS-only requirement.

Deleting an additional Custom Domain releases that domain's addresses. Setting its destination to Unassigned does not release them, and there is no separate release action while keeping the domain. Other domains retain their allocations.

After the Primary Custom Domain is removed, the Files.com subdomain resolves to the general pool. Networks that previously allowed only the dedicated pair need rules covering the shared range and any required service destinations.

Transferring an AWS Elastic IP Address

Files.com supports transferring in an AWS Elastic IP address in supported AWS regions. This is separate from allocating Files.com addresses or bringing an owned address range. It is available exclusively on Enterprise plans and requires approval and coordination with Files.com. Extra charges apply outside the eight AWS regions where Files.com maintains proxy infrastructure. Contact your Account Manager or Files.com Support to coordinate the migration.