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 share 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.
Anstatt random Zöllen einfach mal #IPv4 abschalten, weil ist ja sowieso alles Frei.
After a fair bit of tinkering in between things I’ve finally gotten my BGP bits sorted properly and sending announcements up to my peer, some further filters adjusted in the peers link to the carriers and I’m now routable to the world!
Hello le #fediverse ! J'envisage peut-être de passer mes instances #peertube, #friendica, #pixelfed et #mastodon vers des serveurs full #ipv6 (des tests sont en cours avec pixelfed), ce qui me permettrait d'avoir une ip publique différente par machine, ce qui n'est pas le cas avec #ipv4, tous mes services tournent sur une même machine (ça fonctionne mais ce n'est pas très safe). Êtes-vous prêts pour le 100 % #ipv6 ? Vos réponses m'aideront à prendre une décision
Проброс сайта, не имеющего глобального IP-а́дреса, из локальной сети на свой сервер в Интернете (обратный прокси) через сеть Yggdrasil
https://multed.com/2024/04/03/nginx-and-yggdrasill.html
Just had a hair-tearing situation (and I already have barely any hair left) where @letsencrypt certbot simply refused to create a key/cert pair on a @debian server.
Turned out to be a domain with a mix of IPv4 and IPv6 #DNS records. #IPv4 were changed, #IPv6 not.
https://www.claudiokuenzler.com/blog/1480/lets-encrypt-certbot-error-mixed-dns-records-ipv4-ipv6
Today, when looking into #ipv4/#ipv6 issues, I learned about #happyeyeballs (https://en.wikipedia.org/wiki/Happy_Eyeballs).
Such a pretty name for such an annoying problem.
Question to the network people out there:
Are there any ISPs that are IPv6 only (without providing a NAT/whatever)?
Background: Having an argument with a provider that hasn't published any AAAA records, and whilst I think that's poor form, I'm wondering if this would actually negatively affect any actual users in practice?
@DoctorBrodsky @woe2you @miah given #Quad9 bowed before the #Contentmafia and censored #DNS requests, I'll continue to recommend using #OpenNIC's Servers instead
94.103.153.176 & 2a02:990:219:1:ba:1337:cafe:3
as well as144.76.103.143 & 2a01:4f8:192:43a5::2
I merely retain quad9 on said list for archival purposes. I Yeeted #CloudFlare aka. #ClownFlare since they are a #RogueISP!
#IPv4-Adressen als Wertanlage
I do that with #pfSense & #OPNsense (depending on the exact network in question) and have it merge multiple sources that get cached.
In total, I do may out the 30 DNS servers and whilst I have #IPv4only, I have everything ready for #DualStack (#IPv4 + #IPv6) once my ISP stops keeing it's thumbs um their ass...
Разработка скрипта для распознавания капчи Cloudflare
https://habr.com/ru/articles/892986/
Я понимаю, что иногда Cloudflare используют, чтобы скрыть настоящий #IP-адрес сайта. Или чтобы сайт, у которого нет #IPv4-адреса, был доступен и тем пользователям, у которых в 2025 году почему-то всё ещё нет #IPv6. Было бы лучше, если бы каждый сайт за Cloudflare был доступен также в скрытосетях: #Tor #onion, #I2P.
It would be nice if infosec and IT tools provided better IPv6 support.
Weren't we supposed to run out of IPv4 addressees 10 years ago? What happened to the IPv6 revolution?