Overview
This article is intended for ARS Level 2 techs who need to configure IPv6 on AWS Servers maintained by ARS. It discusses three aspects:
1.) Enabling IPv6 connections into AWS VPCs on a region by region basis. (ARS places all of customer servers in a single VPC for a given region in AWS.) This is done only once per region.
2.) Enabling IPv6 for an individual AWS EC2 Server
3.) Updating that Server’s DNS entry at “site5 web hosting”, the DNS service that ARS uses.
Important: You should not do steps 2 or 3 for a particular server until R5 has been installed. Previous versions of RMA do not RMA do not support IPv6. Enabling IPv6 for them could, in some circumstances cause incoming connections from IPv6-only clients to be connected to an IPv6 socket that RMA is not listening on. (I believe this is correct, but am double checking with Frank and Chris.) Note that RFC 4472 section 4.3 recommends not configure IPv6 DNS for servers not ready to support it.
This article was created because T-Mobile has some areas where they offer only IPv6 support and no IPv4 support. In these areas, the handhelds cannot connect to RMA unless the RMA server is on R5 or above and IPv6 has been configured for their AWS server as described in this article.
Although we have not encountered it yet, if the customer has their own on premise server and DNS provider, then similar configurations would need to be done on their routers and DNS provider. This article does not address these non-AWS configurations.
Cause
Cell phone providers that force the usage of IPv6 versus IPV4.
Resolution
1. Enabling IPv6 for the region (Done ONCE per region)
<< Need to indicate where to do this? on a server? >>
1) Click on Services and search for VPC
2) Click "See all regions"
3) Choose the region where you want to enable IPv6
4) Right click on the default VPC and left click "Edit CIDRs"
5) Click "Add IPv6 CIDR" and it will then show a new IPv6 CIDR associated with the VPC.
6) Click "Close", then in the left menu pane, click Subnets
7) Right click the Subnet and left click "Edit IPv6 CIDRs"
8) Click the "Add IPv6 CIDR" and start with 00 and increase one for each "Subnet"
9) Click save and repeat from Step 6 for each Subnet... remember to increase each IPv6 by 1.
10) In the left menu pane, click "Route Tables" then click on the "Routes" tab
11) Click the "Edit routes" button and then the "Add routes" button
12) Add the route with "::/0" for the Destination and copy the "Target" from the 0.0.0.0/0 record and then click "Save routes"
2. Enabling IPv6 on an EC2 Instance (Per EC2 Instance)
1) Click on Services and search for EC2
2) Click on Running Instances
3) Right click on the instance you want to add an IPv6 and then choose Networking > Manage IP Addresses
4) Click "Assign new IP" and then the "Yes, Update" button
5) Copy the IPv6 into your clipboard
6) You're done with AWS.
3. Enabling IPv6 in the DNS on Site5
1) Log into Site5 for the DNS changes
2) Click on "Services" and then "My Services"
3) Click the "Active" button for "ars247.com"
4) Click "Login to cPanel"
5) Click "Zone Editor"
6) Click the "Manage" link for ars247.com
7) Click the "Add Record" drop down and then choose "Add AAAA Record". (An "AAAA" record is an IPv6 address record.)
8) Add the host name in the "Name" field, the IPv6 in the "Record" field, and then click "Save Record"
9) If the shXXX record is CNAME, then you need to add the "AAAA" record to the name containing the "A" record.
IMPORTANT! You must make the TTL (Time To Live) parameters for IPv4 and IPv6 the same! (The IPv4 record has a type of "A". The IPv6 record
10) You can monitor the propagation at "https://dnschecker.org" and changing the drop down to "AAAA".
More Information
ONLY server administrators should be preforming this task.