IPv6 compatibility - jupiterbroadcasting.com does not have IPv6 compatibility

[TeamLinux01]

It seems that there are no AAAA name records for IPv6. Please serve the website on IPv6 as well as IPv4.

https://dnschecker.org/ipv6-compatibility-checker.php was used to quickly check compatibility.

[elreydetoda]

To help fix this, since JB already uses cloudflare for their DNS, maybe it should be considered to use more features of Cloudflare (i.e. their IPv6 compatibility gateway). This'll help with the IPv6 issue (for both .net + .com) and not require any extra work on the backend server side.

I see that the .com's IP address points directly to ScaleEngine's IP address, so it seems like they might be grey-clouding the JB website instead of proxying then DNS requests (src). If JB was to proxy their DNS requests (orange-cloud), then they'll also get IP address masking (which helps protect the origin from mean people) as well as built-in DDoS protection.

For example, I have the IPv6 gateway enabled on my blog: https://blog.elreydetoda.site
But the Digital Ocean droplet only has IPv4 support (not going to post my whole IPv4 address, since it'll give away my blog's IP address 😅 ). I ran this from my droplet though and it can't connect over IPv6 getting forced by curl.

But you can navigate to it from IPv6 only machines (run on my android phone via termux).

[gerbrent]

great suggestions!

[TeamLinux01]

I just want to see more things that use IPv6 so that one day we can get away from IPv4. As long as it doesn't get forgotten about, I can wait. 😁

[elreydetoda]

Ya, I completely understand @TeamLinux01, and it was a good suggestion for milestone 1.0 😁

My proposed solution wouldn't require really any work from a server hosting side, and we'd be taking care of our IPv6 breathers 😅

One important reason to ensure that it's compatible, is that if someone that is only IPv6 tries to navigate to the site now...they wouldn't be able to connect to it (since we don't have an IPv6 endpoint/IP address). So, it's an important request to make sure we reach as many people as we can 😁

[elreydetoda]

BTW, once JB.net is moved to dev.JB.com it looks we'll be able to close this issue 😁

[gerbrent]

I've been advocating for this one throughout!

[elreydetoda]

Thanks @gerbrent 😁

I think it's awesome that JB is doing this, because just like Chris says all the time with stuff "If we aren't doing it and we've got a technical audience who will" (summary of course 😅 )

[ironicbadger]

How do our new deployment schemes affect this? new.jb.com for example...

[elreydetoda]

From my perspective, I don't think this will be accomplished until we get Cloudflare DNS proxying implemented. That'd be the only way we could do the IPv6 Gateway feature and it'll transparently handle IPv6 addresses (like I mentioned above: #16 (comment) ).

It was working when the dev.jb.com was created, but we don't have the proxying for the new.jb.com.

I posted this in matrix, would this work?

Just heard in LUP you all use ansible to control DNS instead of terraform, so would it just be adding proxied to this file?

The only other alternative would be to deploy the server with IPv6, which I don't feel comfortable recommending, because there is so many security things to think of with that 😅

[elreydetoda]

This is now working with the new.jb.com domain: #292 (comment)

But since it wasn't enabled for the main domain jb.com (source), this issue should probably still stay open.

[elreydetoda]

Now with this #355 & JupiterBroadcasting/infra#5 and validating with the picture below we can now close this issue! 🥳

Thanks @TeamLinux01 for submitting this 😁