IPv6 Frequently Asked Questions

IPv6 (Internet Protocol version 6) is an IP addressing scheme used to identify the source and destination when two computers or devices communicate over the Internet. IPv6 is the successor to IPv4 (e.g., 10.10.10.101).

IPv6 is needed to address the rampant growth of the Internet. This growth will eventually exhaust the set of available IPv4 addresses. IPv6 dramatically increases the number of available addresses when compared to IPv4.

Existing IPv4 network traffic will not be affected by the introduction of IPv6 support. Rather, IPv6 support allows a different type of network traffic (i.e., IPv6) to be delivered through our CDN. IPv6 network traffic is handled by our IPv6 edge servers. If the requested content has not been cached, then the request will be forwarded to your customer origin server. This will occur regardless of whether you have associated IPv4 or IPv6 servers with your customer origin configuration.

The following CDN settings/pages have been updated to support IPv6:

• A customer origin can be configured to point to a server that has been assigned an IPv6 address. This optional configuration is not required to handle IPv6 traffic. Our edge servers can accept IPv6 traffic on your behalf and then send it to a customer origin server that has an IPv4 address.
• The Customer Origin page now lists two sets of IP blocks (IPv4 & IPv6) used by our edge servers. Each server associated with a customer origin configuration should not restrict access from the IP blocks corresponding to their IP-type. In other words, IPv4 servers should not restrict access from the IP blocks for IPv4, while IPv6 servers should not restrict access from the IP blocks for IPv6.
• The Client IP Address match condition in Rules Engine can match IPv6 addresses.
• The REST API supports the use of IPv6 notation by most operations that allow an IP address to be specified. Notable exceptions are legacy operations.
• The IPv4/IPv6 (Data Transferred) report allows you to compare the amount of data transferred between IPv4 and IPv6.

The proper notation is either one of the following:

IPv6 notation uses colons. URIs/URLs already use the colon character to indicate the port through which communication will take place. Therefore, standard URI/URL notation requires that an IPv6 address be enclosed within brackets to indicate the end of the IP address.

The proper notation is either one of the following:

Unlike customer origin configurations, other platform features (e.g., Rules Engine's Client IP Address match condition) do not require a URI/URL. They simply require an IP address.