Wie wäre es, ihr kümmert euch mal um den #IPv6|-Rollout auf social.bund.de? Ja, ihr müsstet dafür entweder Fa. T-Systems etwas bearbeiten oder den Hoster wechseln. Aber es lohnt sich, weil euch dann endlich die Grundfunktionen der genutzten Dienstleistung zur VErfügung stehen würden! @Bundesregierung
The slime also evolves, apparently. Today https://nxdomain.no/~peter/wankstortion/20250416_jevkisca@teksavvy.com_me@pmg-pub-smtp1.teksavvy.com.txt (https://nxdomain.no/~peter/wankstortion/20250416_jevkisca@teksavvy.com_me@pmg-pub-smtp1.teksavvy.com_original_base64.txt) inboxed, as far as I can recall the first #wankstortion message received here over #IPv6 (and likely inboxed for that reason, bypassing the IPv4 only #spamd).
See "The Despicable, No Good, Blackmail Campaign Targeting ... Imaginary Friends?" https://nxdomain.no/~peter/despicable_no_good_blackmail.html and links therein for some background #cybercrime #scams #sextortion #bitcon #bitcoin #cryptotulips #cryptocurrency #extortion #teksavvy
I left Plusnet in 2020 because of their radio silence on IPv6. I’m quite happily on Zen now but good to see more UK ISPs on the way to getting #IPv6.
https://mastodon.social/@ispreview/114346388264504143
New Blog Post: IPv6 Support in Public Docker Registries in 2025
https://blog.miyuru.lk/ipv6-docker-registries-2025/
Let me know any other docker registries , that I have missed. I will check and update the post.
Noob-level #SelfHosting #IPv6 question:
My home computers are connected through a router and, although they're clearly using NAT through said router for IPv4, they appear to all have outside IPv6 addresses. Are those addresses directly accessible from outside? When adding AAAA records to my outside DNS zones, should they point to my router's address, or the target machine's?
Nice! @tailscale finally updated their infrastructure to support IPv6-only OIDC endpoints (after I complained)
Where would I need to go, if I wanted to address each individual pixel of my monitor via an #IPv6?
As someone who until the past year or so had not really taken the time to (seriously) consider using #IPv6 ....
finding this gist has really made this feel like it *might* actually be not *quite* as scary as I'd always envisaged..
I honestly wish I'd understood sooner that devices could be set to only use IPv6 ULAs (Unique Local Addresses), and as a result be unreachable *directly* from the internet sooner!
I had always envisaged a need to carefully operate and maintain firewalls directly on all individual local only devices.
https://gist.github.com/timothyham/dd003dbad5614b425a8325ec820fd785
Is there anything I should be mindful/aware of, or think about, in addition to the points highlighted in this gist?
If this helps gets me from IPv4 only to IPv6 mostly, I hope I can contribute anything "extra" mentioned in replies (and/or from my own experience) back to the gist, and hopefully help others in the process!
TIA! 
Just wanted to share some thoughts on #RFC9715 - an #RFC that defines standards on reducing the #DNS issue of IP fragmentation over #UDP. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the #Internet. A great leap forward to (hopefully) reduce the reflection/amplification #DDoS potential of DNS.
Just today I learned that #Google will configure their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to #TCP.
So I want to do something ridiculously stupid with IPv6 because science.
I know one pays for an allocation, I'm assuming one gets an AS record and ARIN handle. Anything I should know before requesting an IP block?
@matdevdug According to https://github.com/netbirdio/netbird/issues/46 Netbird still does not support the *current* Internet Protocol. I've evaluated it last year to replace the #IPSec VPN at $WORK and lack of IPv6 was the reason I had to give up on Netbird. I have quite many #IPv6 -only hosts and my colleagues need to be able to access them.
Oops! The MXP01 (Italy) peer had some fuck ups, followed by some insane traffic f*ckups at 3AM & 6AM on the other instances.
Rule Nr. 1: Even changing a single character can result in f*ckups. Always test!
new freebsd PR: merge traceroute6 into traceroute
Looks the @internetarchive crawler has IPv6 now. Using their own ASN.
https://web.archive.org/web/20250405000858/https://ipv6.icanhazip.com/
![A screenshot of a web browser attempting to make a connection to a website using the address https://2a04:4e42::820
The error message is as follows:
Requested host does not match any Subject Alternative Names (SANs) on TLS certificate
[afde811d2be66338F3f f6da60e6b92fc301cc816eb27d3b05a2b323b892c3fF] in use with this connection.
Visit https: //ww.fastly.com/documentation/guides/concepts/errors/#routing-errors for more information.](https://cdn.fosstodon.org/media_attachments/files/114/286/227/817/751/545/original/201d539c68499253.png "A screenshot of a web browser attempting to make a connection to a website using the address https://2a04:4e42::820
The error message is as follows:
Requested host does not match any Subject Alternative Names (SANs) on TLS certificate
[afde811d2be66338F3f f6da60e6b92fc301cc816eb27d3b05a2b323b892c3fF] in use with this connection.
Visit https: //ww.fastly.com/documentation/guides/concepts/errors/#routing-errors for more information.")
Yggdrasil is a new experimental compact routing scheme. It is designed to be a future-proof and decentralised alternative to the structured routing protocols commonly used today on the Internet, as well as an enabling technology for future large-scale mesh networks.
#ipv6
https://yggdrasil-network.github.io/
Bummer. fosstodon.org's host doesn't support #IPv6
