3 ms·

There's a lot more work for IPv6 support than just throwing a AAAA record on a domain. A few of them: - IPv6 Peerage. - An IPv4 or IPv6 broker. - First party

There's a lot more work for IPv6 support than just throwing a AAAA record on a domain. A few of them: - IPv6 Peerage. - An IPv4 or IPv6 broker. - First party software configuration. - Support from upstream and downstream from infrastructure/partners and configuration. It is a significant project. People think you just assign an IPv6 IP, throw in a AAAA record, and then it magically just works. More than likely you'd just create a block-hole where IPv6 traffic goes to die.

bauruine 3y ago
hn has two servers at m5hosting which according to their FAQ [0] "IPv6 support is currently available for Dedicated Servers or Colocation." so you ask support, they assign you a prefix and you add a few IPs from that prefix. done. My guess is their anti spam or something else in the software expects an IPv4. [0] https://www.m5hosting.com/support/cloud-faq/ https://www.m5hosting.com/support/cloud-faq/
toast0 3y ago
IPv6 is work, but it's not that much work if your networking or hosting provider already supports it (as is claimed in this case). Address classification changes are real work. I haven't done heavy benchmarks, but bigger addresses and everything else probably does add up to a measurable server performance drop, but that's balanced by real world networking performance improvements for users with nasty network stuff on IPv4 and less for IPv6. Otoh, I'd guess HN isn't bottlenecked by networking anyway.
bombcar 3y ago
For many sites all you need is the AAAA record. But something like HN probably has various moderation/spam preventing tools that assume IPV4. I believe people have made IPv6 gateways to the ipv4 content.
housemusicfan 3y ago
> More than likely you'd just create a block-hole It's still called a black hole. https://en.wikipedia.org/wiki/Black_hole_(networking) https://en.wikipedia.org/wiki/Black_hole_(networking)
- joeframbach 3y ago
  Sounds like someone didn't get the inclusive language memo.
  - simfree 3y ago
    Sounds like you need some Neil Degrasse Tyson ASMR: https://www.youtube.com/watch?v=kK1QciF-t5k https://www.youtube.com/watch?v=kK1QciF-t5k
ZeroSolstice 3y ago
I think that if you are in a position where you are hosting your own infrastructure in a data center these wouldn't be difficult issues to address and are the bare minimum in running that type of operation. You can front any website with a load balancer that proxies the connection to a IPv4 only back end and the major web server software such as Apache and Nginx supports v6 natively. If you aren't hosting the infrastructure yourself then you are limited in what you can support but you wouldn't be worried about peering, brokers, or up/downstream providers since thats what you would be paying the hosting provider for.

bauruine 3y ago

hn has two servers at m5hosting which according to their FAQ [0] "IPv6 support is currently available for Dedicated Servers or Colocation." so you ask support, they assign you a prefix and you add a few IPs from that prefix. done. My guess is their anti spam or something else in the software expects an IPv4. [0] https://www.m5hosting.com/support/cloud-faq/ https://www.m5hosting.com/support/cloud-faq/

toast0 3y ago

IPv6 is work, but it's not that much work if your networking or hosting provider already supports it (as is claimed in this case). Address classification changes are real work. I haven't done heavy benchmarks, but bigger addresses and everything else probably does add up to a measurable server performance drop, but that's balanced by real world networking performance improvements for users with nasty network stuff on IPv4 and less for IPv6. Otoh, I'd guess HN isn't bottlenecked by networking anyway.

bombcar 3y ago

For many sites all you need is the AAAA record. But something like HN probably has various moderation/spam preventing tools that assume IPV4. I believe people have made IPv6 gateways to the ipv4 content.

housemusicfan 3y ago

> More than likely you'd just create a block-hole It's still called a black hole. https://en.wikipedia.org/wiki/Black_hole_(networking) https://en.wikipedia.org/wiki/Black_hole_(networking)

joeframbach 3y ago
Sounds like someone didn't get the inclusive language memo.
- simfree 3y ago
  Sounds like you need some Neil Degrasse Tyson ASMR: https://www.youtube.com/watch?v=kK1QciF-t5k https://www.youtube.com/watch?v=kK1QciF-t5k

ZeroSolstice 3y ago

I think that if you are in a position where you are hosting your own infrastructure in a data center these wouldn't be difficult issues to address and are the bare minimum in running that type of operation. You can front any website with a load balancer that proxies the connection to a IPv4 only back end and the major web server software such as Apache and Nginx supports v6 natively. If you aren't hosting the infrastructure yourself then you are limited in what you can support but you wouldn't be worried about peering, brokers, or up/downstream providers since thats what you would be paying the hosting provider for.