This article outlines best practices for allowlisting IPv6 addresses in Government Cloud Plus. Salesforce supports dual-stack IPv4/IPv6 connectivity once IPv6 is rolled out to your specific instance, and allowlisting the correct address ranges helps your organization maintain secure, uninterrupted connectivity. If you have any questions about allowlisting IPv6 addresses for your org, contact Salesforce Support or your Account Team.
Work with your network team to identify your public IPv6 address space before you start allowlisting IPv6 addresses for your Salesforce org.
From Setup, enter Trusted IP Ranges. Allowlist the relevant IPv6 addresses from your public address space to your org's Trusted IP Ranges and user profiles' Login IP Ranges. Do the same if you're using a third-party (content delivery network) CDN, like Akamai or Cloudflare to serve content from Salesforce.
If you're using Connected Apps, allowlist each Connected App's IPv6 address space into its Connected App configuration.
Select the Connected App to update, then update the IP Relaxation policy.
Allowlist IPv6 addresses to accept your integration's IPv6 traffic policy.
Allow IPv6 Connectivity from Salesforce Back to Your Network:
Allowlist Salesforce's published IPv6 ranges across your internal network — proxy servers, firewalls, CDNs, APIs — so you can receive IPv6 traffic from Salesforce.
Don't remove your IPv4 addresses when you add IPv6. You can allowlist up to 2^24 (16.8M) IPv4 addresses and 2^99 IPv6 addresses. See Set Trusted IP Ranges for Your Org for details.
Review your Session Settings to avoid login issues once IPv6 addresses are allowlisted.
Salesforce supports dual-stack IPv4/IPv6 once IPv6 is rolled out to your instance. If you can't support IPv6 at all, block traffic from Salesforce's IPv6 addresses on your firewalls. See "IP Addresses to Allow for Government Cloud Plus Customers" for the specific ranges.
005386015

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.