SimplerCloud Pte Ltd

×
×

(Ended) How would the IPv6 test-bed implementation affect our servelets?

Back

Update on 3 March, 2016:

IPv6 beta-testing is concluded.


1. How would you perform the IPv6 test-bed implementation?

At the start of the IPv6 test-bed implementation, we will be enabling IPv6 networking on the VLAN where our customers' public cloud servelets reside. The purpose of doing this is so that we can provide IPv6 connectivity to our customers. This would be done on top of the existing IPv4 network (dual-stack), so there will be no disruption to the existing IPv4 network and the connectivity to your servelets.

2. Will I still be having my original IPv4 address(es) after this implementation?

Yes, your existing IPv4 address(es) will still be intact and will not be changed. You will have additional IPv6 address(es) on your servelet on top of your existing IPv4 address(es).

3. What will happen to our servelet after this implementation?

Most of our servelets' operating systems are configured with IPv6 enabled on the network settings by default. This IPv6 test-bed implementation might cause your servelet(s) to automatically get a random IPv6 address from our router via stateless auto-configuration (SLAAC) and install it on the system.

When that happens, your servelet will start establishing connections to other IPv6-enabled servers using IPv6 network by default. Only when IPv6 connection is not possible, then your servelet will use the normal IPv4 network to reach the destination.

4. Any issues which might happen after this implementation?

No, this implementation should not affect your servelet's network connectivity and reachability to the Internet in general. However, default establishment using IPv6 network might cause some issues for certain applications.

For example, mail server running on your servelet might start sending email traffic to other mail servers via IPv6 instead of IPv4, and can cause email rejection issues, for example, when the recipient mail server recognised the email coming from an IPv6 address and there's no PTR (reverse DNS) record being setup for it.

Update on 12 October 2015: We noted that this email undeliverability issues happen to emails being sent to domains hosted on Google mail server. More information about this and how to resolve the problem can be found on our knowledge-base article here.

To resolve the problem, you would need to open a support ticket for us to configure PTR (reverse DNS) record on the IPv6 address.

5. How to request static IPv6 address for my servelet?

You don't actually need to request a static IPv6 address, since the IPv6 address which is automatically assigned to your servelet via SLAAC is actually static and will not change. You can request for the PTR (reverse DNS) record to be created for the IPv6 address -- please advise on the hostname where you would like to point the PTR record to (e.g. mail.company.com).

6. How to setup PTR (reverse DNS) record for my servelet's IPv6 address?

The setup of PTR (reverse DNS) record for your IPv6 address can only be done by us. Please open up a support ticket providing us with the IPv6 address and the hostname where you would like to point the PTR record to (e.g. mail.company.com).

7. How to install the static IPv6 address into my servelet?

By default, the IPv6 address will automatically be assigned to your servelet via SLAAC. However, if you still want to configure the IPv6 address as a static IPv6 address hard-coded into your servelet's TCP/IP settings, please find below.

Please find below some knowledge-base articles outlining how to install static IPv6 address on your servelets depending on the operating system and/or control panel being used:

Ubuntu - https://my.simplercloud.com/index.php?/knowledgebase/article/182/how-to-configure-static-ipv6-address-on-ubuntu-/

CentOS - https://my.simplercloud.com/index.php?/knowledgebase/article/183/how-to-configure-static-ipv6-address-on-centos-/

We shall update our knowledge-base articles soon on how to configure static IPv6 addreses on other operating systems and control panels.

8. Can you assist to configure the static IPv6 address on my servelet?

Yes, feel free to open a support ticket with us if you need our assistance in installing the static IPv6 address on your servelet.

9. I experienced an issue with my application, which might be due to the IPv6 test-bed implementation. What should I do?

If you notice any issues on your applications which you think cuold be due to this IPv6 test-bed implementation, please feel free to open a support ticket with us. We shall assist you the best we can.

10. What will happen to my DNS settings currently pointing to the IPv4 addresses of my servelet(s)?

The DNS settings should remain intact as it is, and there's no need to change the DNS records. The reason is that the IPv4 address(es) on your servelet will still be intact, they will not be changed or removed.

You might want to consider creating new AAAA records, which is the IPv6-equivalent of A record on IPv4, to point your domain to the IPv6 address of your servelet. However, you would need to ensure that your application can work on IPv6 network and listening on the IPv6 address before you point the AAAA domain record over.

11. I have some licensed softwares which are tagged to the existing IPv4 address of my servelet. Do I need to do anything?

No, you don't have to do anything. The IPv4 address will still be intact and will not be changed or removed. Your licensed software or application will still be able to work under the IPv4 address as per normal.

12. Does it mean that I am now able to access my servelet in both IPv4 and IPv6?

At the moment, we are in the stage where IPv6 address is installed on your servelets on the network (TCP/IP) level, and for your servelet to be able to communicate with other IPv6-enabled devices and equipment. For your applications (e.g. website, email, etc) to run on IPv6, you would still need to configure the applications to run on IPv6 network and listen on the IPv6 address. You might want to consider implementing it in the (near) future when you think that it's compulsory for your services to also run on IPv6 (in addition to IPv4).

13. Will there be any changes on the iptables needed?

At the time when you want to configure your applications (e.g. Apache web server, mail server, etc) to run and listen on IPv6, yes you would need to configure the iptables rules accordingly to open up the ports for IPv6.

Was this article helpful?
Dislike0 Like0
Views: 1995