Cancel
Start searching
This search is based on elasticsearch and can look through several thousand pages in miliseconds.
Learn more
This search is based on elasticsearch and can look through several thousand pages in miliseconds.
Learn moreThe global pool of available IPv4 addresses, from which providers could request additional addresses as needed, has been exhausted since January 2011. The regional pool responsible for our region shrank to a critical level in September 2012; since then, every registered provider has been able to request a one-time block of approximately 1,000 IPv4 addresses, but no further IPv4 addresses are available. Some providers that still have unused IPv4 addresses are willing to sell them; however, these addresses were often previously used for spam and the distribution of malware and are filtered out in many places.
Most Internet service providers therefore face the challenge of offering more services than before—such as additional websites—using their existing stock of IPv4 addresses. punkt.de ’s approach here is to transition services to IPv6 operation as much as possible, where addresses are virtually unlimited. The second generation of our proServer is a result of these efforts.
As before, these are standalone virtual machines with the functionality of a complete operating system. However, the virtual machine now has only an external IPv6 address and no longer has a legacy IP address (IPv4 address).
These are standalone virtual machines that establish the connection to the legacy IP network for multiple vpro containers at a time. Each of these gate64 containers has both an IPv6 and an IPv4 address. Outgoing connections—that is, those initiated from the vproXXXX—can be established via these containers to any destination in the IPv4 range. Incoming connections—that is, those from the (IPv4) Internet to the vproXXXX—are only possible on ports 80 (HTTP) and 443 (HTTPS).
This is also a standalone machine with one IPv4 and one IPv6 address. Using this host as an intermediate station enables SSH/SCP access to the vproXXXX even for developers who only have IPv4 access to the Internet.
Each vproXXXX container is assigned a “responsible” gate64 container. We will provide you with the IPv4 address of this gate64 container when you set up a vpro container. For websites hosted on the vpro, enter an AAAA record in the DNS with the IPv6 address of the vproXXXX and an A record with the IPv4 address of the assigned gate64 container.
Note: Unlike the first generation of proServers, the AAAA record in the DNS is now mandatory, as the gate64 container uses this DNS entry to determine which vproXXXX hosts a website accessed via this record.
If access to the external resource is via a hostname in the DNS, the developer does not need to take any further action: The nameserver used on the vpro returns a “synthetic IPv6 address” for resources that only have IPv4 addresses; this address is then routed through a so-called NAT64 gateway (on the assigned gate64 host) and translated to IPv4 there. From the proServer’s perspective, communication therefore takes place via IPv6; the translation on the gate64 is not visible to the proServer.
If access is via IPv4 address literals (i.e., a numeric IPv4 address entered directly), such a literal must be converted to the corresponding IPv6 address. This is done by prefixing it with 64:ff9b::/96. For example, the IPv4 address 192.0.2.3 would become the “synthetic” IPv6 address [64:ff9b::192.0.2.3], and the result is then used like an IPv6 address literal. To ping the target system, you would therefore use
ping6 64:ff9b::192.0.2.3
.
There are some operational limitations due to the fact that incoming connections from the IPv4 Internet are only possible via ports 80 and 443 (as well as 22/SSH via a jump host).
If these restrictions pose a problem for your application, please contact us. Together, we will find a solution.