Oracle Cloud Infrastructure Documentation

IPv6 Support for OCI Cache

OCI Cache supports IPv6 for OCI Cache API endpoints and Cache cluster private endpoints.

Before creating or connecting to an IPv6-enabled OCI Cache cluster:

  • Use an IPv6-enabled VCN.
  • Use an IPv6-only or dual-stack IPv4/IPv6 subnet for the OCI Cache cluster and client in regions where OCI Cache IPv6 support is available.
  • Ensure that the application host has an IPv6 address and a private network path to the cluster.
  • Configure route tables and security rules to allow the required traffic.
  • Allow stateful TCP traffic on destination port 6379 from the application network to OCI Cache.
  • Use a TLS-enabled Redis or Valkey client.

For information about VCNs, subnets, routes, and IPv6 security rules, see IPv6 Addresses.

Using the OCI Cache API Over IPv6

The OCI Cache API supports both IPv4-only and dual-stack endpoints. Existing IPv4-only endpoints continue to be available. Dual-stack endpoint support is currently available only in the OC1 realm.

You can use IPv6 support in the following way:

  • API: Use the dual-stack API endpoint format: https://redis.<region>.ds.oci.<domain>

    The ds label identifies the dual-stack endpoint.

For information about IPv4-only and dual-stack OCI service endpoints, see IPv6 Support.

Connecting to Cache Clusters Over IPv6

To connect to an OCI Cache cluster over IPv6, create a new cluster in an IPv6-capable virtual cloud network (VCN) and subnet. Existing Cache clusters aren't upgraded to support IPv6.

OCI Cache supports IPv6-only and dual-stack client subnets.

When IPv6 is enabled for a cache cluster, the following endpoint fully qualified domain names (FQDNs) publish AAAA records:

  • Primary endpoint FQDN
  • Replica endpoint FQDN
  • Sharded-cluster node endpoint FQDN
  • Discovery endpoint FQDN

Configure applications to use OCI Cache endpoint FQDNs for normal connections and topology discovery. Don't configure applications with literal IP addresses. Use a literal IPv6 address only to test IPv6 connectivity.

To look up the IPv6 address for an endpoint FQDN, use a DNS AAAA query. For example:

dig AAAA <endpoint> +short

The client must have private network connectivity to the cache cluster. Use the same private routing and security model you use for IPv4, and add IPv6-specific rules as needed:

  • Add the IPv6 CIDR for the client subnet as the source in the cache ingress rule.
  • Allow stateful TCP ingress on port 6379 to the cache endpoint.
  • Allow the corresponding egress from the client subnet.

For information about configuring IPv6 addresses, VCNs, subnets, routing, and security rules, see IPv6 Addresses.