Some debugging on the discord part (one of the people I live with will kill me), they either hard coded a resolver or resolve from somewhere else and send an IP address instead of resolving locally ._.

I don't want to continue to debug this or even try to bully someone at discord for this shit... aaagony

@famfo As much as I enjoy being able to remember my server's IP addresses from memory, I'm genuinely kind of shocked that IPV6 isn't more widely adopted considering how """urgent""" it was 15 years ago and how they've invested in trying to keep v4 alive as long as possible instead.

My home ISP has an entire website dedicated to tracking whether we have it yet :^) https://www.havevirginmediaenabledipv6yet.co.uk/

@famfo I kept a ticket with Discord alive for a year about that crap. I ended up leaving it long enough they silently closed the ticket. I tried to open a new ticket and refer to the year-long one but they decided to ignore it.

@famfo 26 years old and deployed in production since before 2012. It's already sad enough when an application still doesn't support v6 in 2024, but hardcoded v4 dependencies are just ridiculous.

That wouldn't be a problem however if all operating systems had CLAT support, which would allow you to use 464XLAT like most big 4G/5G providers... 😒

Update 2, I have set up a DHCP server again :/

I am still advertising only the DNS64 over SLAAC so I can make some fun graphs of apps with hardcoded IPv4 DNS servers. The only issue with this setup: systemd-networkd may be able to do everything but it falls apart way too quickly when just leaving it a night, I'll just setup udhcpcd again.

@famfo It has been a while since I last tested it, but Discord WebRTC seemed to work fine on a Mac. I think that is because the Mac's CLAT kicked in and made it work.