IPv6 has been developed to replace IPv4 which is running out of addresses.
Although it has been around almost 12 years it is still not widely deployed and supported.
However, adoption rates are increasing rapidly and IPv6 traffic crossed the 10% threshold in February 2016.
Hosting Bot, LLC has fully deployed its IPv6 infrastructure and is already implementing "Dual Stacking" across its product lines and has begun offering products using sole IPv6.
We are aware of the issues that could arise with sole IPv6 addressing on Virtual Systems and are here to provide a guide to our customers for common issues that could arise and ways to correct them.
- You may find that you are not able to connect to certain addresses because those addresses have not been deployed or do not support IPv6 addressing. Common error messages on Linux are as follows: "curl: (7) Couldn't connect to server" or "Ping: address specified by you: No address associated with hostname
How do I go about correcting these errors?
- For starters, this is not a Hosting Bot, LLC infrastructure, virtual machine, or operating system-related issue, but the sheer fact the server or domain you're attempting to connect to or ping does not support IPv6. In these situations, it is recommended that you contact the domain or servers administrator and request that they implement IPv6 support. In the meantime, Hosting Bot, LLC acknowledges this pitfall in IPv6 and will provide a temporary IPv4 address to those who need it at an hourly rate so that customers who need to connect to an IPv4-only server or host can do so.
- Additionally, customers can also use the dual stacking method and purchase their own dedicated IPv4 address from Hosting Bot, LLC for $2/m along with their IPv6 Subnet. Both addresses will work in unison with each other and will allow for both IPv4 and IPv6 connections simultaneously.
A second issue that is very common with IPv6 is receiving a "Permission Denied" error when attempting to SSH/RDP to your Primary IPv6 address.
- This is typically a Firewall issue with your home router, typically provided by an ISP or your main computer systems firewall blocking the port or IPv6 in general. If it's an ISP router, you can simply call your ISP and ask them to allow for connections over IPv4 and IPv6 and unblock outbound connections to port 22. Please note Hosting Bot, LLC does NOT inherently block port 22 or IPv6 so the issue is almost always this.
- Also, don't forget to ensure your computer is not blocking port 22 as well, contact your computers system administrator (if applicable) should you need assistance.
To learn more about IPv6, check out: This
