IPv6 Only Cloud Server
v6node.com
v6node.com
Edit: The ToS say "The Website is offered by canvay.io, located in Karlsruhe, Germany". Dude, with all due respect, get your shit together. As a German citizen/company, you MUST publish an imprint with a company address, a VAT etc. [1].
It looks like a genuinely nice service, but it is just a matter of time until someone sends you a cease-and-desist order, which will be a lot more expensive than getting a proper imprint. And also, you'll earn more trust.
If you incorporated as a sole proprietator and want to protect your private address, sign up for a desk at a local coworking space and put that address online.
That said, it's not clear if these VMs have outbound NAT for IPv4 or not. If they do, then what I wrote above won't be a problem.
Founder here, yep you're totally right, BitTorrent and this kind of application won't work as there's no outbound NAT. It's on the todo list however.
Bu pretty much everything else works just fine, e.g. hosting docker containers, Webservers, databases..
Cheers Ian
I'm curious, how would you support this usecase?
Your server won't be reachable over IPv4 from the outside, but it'll work to access most IPv4 exclusive services.
Alternatively, simple carrier grade NAT, possibly using 4over6, can also work. You would provide servers with an internal IPv4 address that would get NAT'ed just like on residential homes.
Most other OSes like Windows also have a built in CLAT implementation that works similarly.
Source: The IP listed in one of their examples is 2a01:4f8:a0:380b::1. If you lookup the ASN it points to Hetzner.
> or ask your ISP to enable IPv6 on your network
Try pulling that with Bell Canada. It’s not coming and they don’t care.
(For context, I am behind @BellNoIPv6 on twitter)
It's OK. I've decided that even when my house has IPv6 native, the Hurricane Electric tunnel is still quite useful to me. Static addresses are always nicer than dynamic.
They point out that offering v4 as a separate line item leads to conversations with accountants about "what's this line item, and do you actually need it?"
"Yes, if we don't have it, we can't reach ~60% of the world's Internet users."
>Assign Primary IPs to your server to establish a connection to the internet. Or create a private-network-only cloud server by not adding any Primary IPs at all. You can change the selected network option at any time.
Management API is Kubernetes only, similar to AKS or EKS.
Networking is IPv6 only, public routeable all the way down to individual pods.
Only entire physical servers can be requested as nodes.
The only other services available are the bare essentials: IPv4 to IPv6 ingress, DNS, key vault, and blob storage.
Functionally, there's little difference between a private /8 or a DHCPv6 /64 except that you can serve even more hosts.
I don’t think AWS will maintain its dominance organically forever. Cracks are already showing. There are too many expensive managed services; maybe fine if you have the budget, but for cash starved startups? Maybe a dead simple cloud provider that goes 90% of the way is good enough.
So you're not paying for the private key storage, you could do that in AWS KMS for like $1/month. You're paying for the CA API.
I could build that service in a weekend(tm)!
Your website says you're planning to put servers in the U.S. - wanted to plug Dedipath: https://dedipath.com/
I'm completely unaffiliated but I had a chat with their CTO Ernie Quick a few weeks back. They seem like a cool team, are pretty reasonable with how they approach billing and network, and they cover the initial rack and stack if you mail them the hardware. They're also the only colo provider I found servicing my area that offers upfront pricing in a Digital Ocean style web UI which I thought was cool!
You could put it in tiers: S gets 1 port, M 4, L 16, XL 64,...; or something like "get a chunk of 50 ports for 1 Euro/y extra"; or combination of both.
Also, there are cheaper options without NAT64 (really IPv6 only).
https://lowendspirit.com/discussion/3981/nl-ipv6-only-kvm-vp...
Will the client's local machine/browser, DNS, and all the routers in between be able to handle a full IPV6 connection with no IPV4?
Or will I have to run a tunnel of some sort?
The idea is to use the built-in reverse proxy for proxying HTTP(S) requests and provide an IPv4 + IPv6 endpoint for your domain.
That means your end users won't even notice the server is running on IPv6 only
Google has some interesting stats on the IPv6 adoption rate: https://www.google.de/ipv6/statistics.html
Do you know if the average person in America will be able to access an IPV6 site from a browser without a reverse proxy of any sort?
Seems a bit odd...
It's sad that we still need NAT64 at this point, especially for a server that's only serving IPv6 requests anyway. At least it brags a complex DS-lite setup at the cloud provider, I suppose.
In American English and the Queen's English, "I don't have IPv6, how to access my node?" is bad grammar and should be "I don't have IPv6, how do I access my node?". As a German selling things in Euro, you are clearly using International English and are free to make your own rules - (I do see this sentence structure a lot with non-native speakers). If that is the standard, us Americans will happily mind our own business. Not sure about the Brits.
So even IPv4 only clients can reach your domains
I know this might look like a small detail, but ipv6 geeks care about this kind of stuff :)
Since we're talking... Do you also delegate the reverse dns zone for the subnet you provide?
Source: https://auctions.ipv4.global/prior-sales
So a /16 (like a cloud provider would be buying) is $3.5M USD right now.
Some providers rent their ipv4 blocks rather than purchase them, because the smallest volume you can buy in is 1024 addresses which is pretty expensive, especially for newcomers. In that case there would be an ongoing cost.