hey #mastoadmin folks:

did you know that you can make the experience for users on mobile data networks faster by making sure your instance is accessible over IPv6?

This is because in a lot of mobile data networks nowadays, IPv4 connectivity is provided via CGN device (Carrier Grade NAT) and IPv6 is provided natively which means that IPv4 is going to be slower.

If your instance's web front end doesn't have IPv6 connectivity, what's the blocker?

a lot of y'all are on server providers that provide IPv6 connectivity and it can be as simple as adding a AAAA record in DNS and making sure your front end web server is listening on IPv6 (which it probably is doing already)


Show thread

If your provider provides IPv6 connectivity and you need help configuring it, hit me up

I'll be glad to help

If you are using masto.host, that's something you need to take up with the folks that run masto.host

Show thread

@packetcat The issue with madto host is OVH's capabilities and how the load balancing (or failover) has been implemented.Last I asked about it, if we were to use ipv6, hugo would need to tell us every time we need to update our dns records.

@ishara ahh I figured it was a issue with the LB system


@packetcat My suspicion is that the root cause is around floating IP addresses. My usual strategy when doing cloud hosting is to reserve a floating IP, put that floating IP in my DNS, and pin that floating IP each time I need to change my underlying VM. I've not found a single provider that supports floating IPv6 addresses, including Openstack.

Sign in to participate in the conversation
Barry Peddycord III

Welcome to my website, powered by the Mastodon microblogging platform!

For more details, visit the about page.