<commit_before>---
title: Enabling IPv6 for Hosted Applications
owner: Routing
---

<strong><%= modified_date %></strong>

The procedure described below allows apps deployed to <%= vars.product_full %> to be reached using IPv6 addresses.

<p class='note'><strong>Note</strong>: Amazon Web Services (AWS) EC2 instances currently do not support IPv6.</p>

<%= vars.product_full %> system components use a separate DNS subdomain from hosted applications. These components currently support only IPv4 DNS resolved addresses. This means that although an IPv6 address can be used for application domains, the system domain must resolve to an IPv4 address.

Complete the following steps to enable support for IPv6 application domains:

1. Set up an external load balancer for your <%= vars.product_full %> deployment. <%= vars.custom_load_balancer %>

1. Configure DNS to resolve application domains to an IPv6 address on your external load balancer.
    <p class='note'><strong>Note</strong>: Your IPv4 interface for the system domain and IPv6 interface for application domain can be configured on the same or different load balancers.</p>

1. Configure the external load balancer to route requests for an IPv6 address to an IPv4 address as follows:
    - If you are using the HAProxy load balancer for SSL termination, route to its IPv4 address.
    - Otherwise, route directly to the IPv4 addresses of the Gorouters.

The following diagram illustrates how a single load balancer can support traffic on both IPv4 and IPv6 addresses for a <%= vars.product_full %> installation.

<%= image_tag 'cf_ipv4_ipv6.png'%>

See [Routes and Domains](../devguide/deploy-apps/routes-domains.html) for more information about domains in <%= vars.product_full %>.<commit_msg>update on aws<commit_after>---
title: Enabling IPv6 for Hosted Applications
owner: Routing
---

<strong><%= modified_date %></strong>

The procedure described below allows apps deployed to <%= vars.product_full %> to be reached using IPv6 addresses.

<p class='note'><strong>Note</strong>: ~~ Amazon Web Services (AWS) EC2 instances currently do not support IPv6. ~~ Now they do support IPv6 </p>

<%= vars.product_full %> system components use a separate DNS subdomain from hosted applications. These components currently support only IPv4 DNS resolved addresses. This means that although an IPv6 address can be used for application domains, the system domain must resolve to an IPv4 address.

Complete the following steps to enable support for IPv6 application domains:

1. Set up an external load balancer for your <%= vars.product_full %> deployment. <%= vars.custom_load_balancer %>

1. Configure DNS to resolve application domains to an IPv6 address on your external load balancer.
    <p class='note'><strong>Note</strong>: Your IPv4 interface for the system domain and IPv6 interface for application domain can be configured on the same or different load balancers.</p>

1. Configure the external load balancer to route requests for an IPv6 address to an IPv4 address as follows:
    - If you are using the HAProxy load balancer for SSL termination, route to its IPv4 address.
    - Otherwise, route directly to the IPv4 addresses of the Gorouters.

The following diagram illustrates how a single load balancer can support traffic on both IPv4 and IPv6 addresses for a <%= vars.product_full %> installation.

<%= image_tag 'cf_ipv4_ipv6.png'%>

See [Routes and Domains](../devguide/deploy-apps/routes-domains.html) for more information about domains in <%= vars.product_full %>.

{'fraction_non_alphanumeric': 0.07399039819260096, 'fraction_numerical': 0.012708274498729173, 'mean_word_length': 4.65814696485623, 'pattern_counts': {'":': 0, '<': 39, '<?xml version=': 0, '>': 39, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3679026', 'n_tokens_mistral': 966, 'n_tokens_neox': 887, 'n_words': 460}