Hacker News Reader

Comment by avitzurel | Hacker News Reader

I really love seeing what DO is doing.

We use a lot of providers, and seeing DO making this available while immediately making the API available is really impressive.

A company that thinks about API first when enabling a new service (like Amazon) enables real developers.

In comparison, we use CircleCI and often you wait for months for features to be available through the API.

View on HN

Have they fixed their IPv6 support yet?

Last i checked, they still issue a single IPv6 address to each droplet (eg a /128, not a /64) and silently block certain ports on IPv6, so no.

Well, I guess they will continue not getting my money then.

Can someone explain the significance of this?

It's basically a non-standard use of IPv6, which is to ideally issue a /64 to each end point. Personally I don't mind, but some people think they need 18,446,744,073,709,551,616 addresses per host.

The idea being with all those addresses you can create subrouters to manage your network topology. Unless you're doing some weird tunnelling setup through your VPS, I can't see why you'd need or want such a huge block.

People complain about only getting a /64 on their home routers.

Blocking certain outbound traffic is another matter: that really stinks.

Who do you use instead? I'm really disappointed by their IPv6 support and undocumented egress firewall rules, but found other providers to have their own set of problems. Would love suggestions.

Vultr has proper IPv6 and is the same price.

Each Droplet gets a /124 block, so 16 IPv6 addresses. Please see this page for more info: https://www.digitalocean.com/docs/networking/ipv6/overview/

Oh my bad. Point still stands.

Reply on news.ycombinator.com