Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Recently¹ tried to bring up a "Flexible" Postgres server (Azure's managed PG offering) on an IPv4 (four) only subnet. The request hung, for two hours, before finally failing with a generic "internal error". Retried, same result. Contact support. Flexible PG doesn't support being brought up on a vnet with IPv6, even if it is on an IPv4-only subnet, even if you have no intention of connecting to it over v6. Want that service? No IPv6 for you, I guess.

¹okay, apparently April, and even just the request to get the limitation added to their documentation of the limitations of IPv6 is still pending…



Hey, you just didn't use the correct combination of SKUs and features. That sums up the standard Azure experience.


You can also not use an IPv4 NAT on an IPv6-enabled network.

Or use Virtual WAN with IPv6... at all.

Or...

It's almost like some subcontractor developer was told to tick a checkbox so that they technically speaking provide IPv6. They do. Technically.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: