Thomas Schäfer
Andreas TaudteWhat you block in #DNS depends strongly on who curates the list. 🤔
That's my takeaway from Branden’s recent #APNIC article on DNS blocking in practice. Especially interesting is how little overlap there was between three blocklists that all aim to identify malicious domains.
Blocking is not just about feeds and tooling, but also about curation, transparency, taxonomy, and context: https://blog.apnic.net/2026/03/04/dns-blocking-in-practice-pdns-in-a-research-and-education-network/
As seen in @andrew_campling ’s weekly "DNS in the News": https://419.consulting/encrypted-dns/f/dns-in-the-news-9th-march-2026
https://blog.apnic.net/2026/03/02/apricot-2026-keynotes-agency-memory-and-getting-ipv6-done/
https://conference.apnic.net/61/assets/presentation-files/07905055-3f90-48af-ac5e-097b9ff91621.pdf
APRICOT 2026 keynotes: Agency, memory, and getting IPv6 done | APNIC Blog
The APRICOT 2026 keynotes set three complementary challenges for the Internet community — use automation without losing agency, preserve the operational record that explains how we got here, and finish the work of IPv6 where it still lags.
GripNews🌗 IPv4 位址「沼澤」：網際網路的新常態
➤ 當例外變成了常態：剖析 IPv4 碎片化對全球路由與安全的深遠影響
✤ https://blog.apnic.net/2025/12/23/the-ipv4-address-swamp-the-new-normal/
在 1990 年代，192/8 等區段因充斥著大量且細碎的 /24 位址分配，被網路工程師戲稱為「沼澤」。然而，隨著 IPv4 位址於 2011 年正式耗盡，這種碎片化的現象已不再是局部問題，而是蔓延至整個網際網路。由於位址稀缺，現今的位址分配更趨向於細分化與頻繁交易，導致全球路由表條目激增至百萬級規模。這種「新常態」不僅讓路由聚合變得困難，更因為位址的高度流動性，為網路安全防護與威脅識別帶來了嚴峻的挑戰。
+ 沒想到以前被視為異類的「沼澤」區，現在竟然變成了全球 IPv4 的縮影。看來路由器的記憶體壓力只會越來越大。
+ 雲端巨頭們瘋狂收購並拆分 IP 段，這不僅是市場行為，更直接改變了網際網路的底層結構，這篇文章的分析非常透徹。
#網路架構 #IPv4 枯竭 #路由技術 #網路安全 #APNIC
➤ 當例外變成了常態：剖析 IPv4 碎片化對全球路由與安全的深遠影響
✤ https://blog.apnic.net/2025/12/23/the-ipv4-address-swamp-the-new-normal/
在 1990 年代，192/8 等區段因充斥著大量且細碎的 /24 位址分配，被網路工程師戲稱為「沼澤」。然而，隨著 IPv4 位址於 2011 年正式耗盡，這種碎片化的現象已不再是局部問題，而是蔓延至整個網際網路。由於位址稀缺，現今的位址分配更趨向於細分化與頻繁交易，導致全球路由表條目激增至百萬級規模。這種「新常態」不僅讓路由聚合變得困難，更因為位址的高度流動性，為網路安全防護與威脅識別帶來了嚴峻的挑戰。
+ 沒想到以前被視為異類的「沼澤」區，現在竟然變成了全球 IPv4 的縮影。看來路由器的記憶體壓力只會越來越大。
+ 雲端巨頭們瘋狂收購並拆分 IP 段，這不僅是市場行為，更直接改變了網際網路的底層結構，這篇文章的分析非常透徹。
#網路架構 #IPv4 枯竭 #路由技術 #網路安全 #APNIC
Dataplane.orgThe Internet Last Week
* Cloudflare outage
https://blog.cloudflare.com/18-november-2025-outage/
https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
https://www.thousandeyes.com/blog/cloudflare-outage-analysis-november-18-2025
https://infosec.exchange/@dougmadory/115570877781768950
* APNIC services disruption
https://apnic.site24x7statusiq.com/#/incident/x0zS3jb7kgn5Q4gW4Lti_TWgsplQIW_HwZIWW_-RexKffYb2ibZqP1JLeqmm8BxBU6heUoM0mfE6aAmdOHnyHA==
* LINX 125
https://www.linx.net/events/linx125/
* AS number block allocation to LACNIC
https://www.iana.org/numbers/allocations/lacnic/asn/
https://orbit.apnic.net/hyperkitty/list/[email protected]/thread/M7LZEP3ECVQRO3IPHB6SGZY7IHXRV46N/
Max ResingAn awesome guest post: Botnets Never Die on the creativity of #malware developers to be found at #APNIC. It covers details to the #AisuruBotnet, The #AIRASHIBotnet, and how their #C2 communication #protocol works.
Apparnetly, the heartbeat is a client sending cat to the C2 server, and the server responds with meow. Fun and creative.
Dan Wing"Analysing the state of Happy Eyeballs implementations" by Patrick Sattler for APNIC, https://blog.apnic.net/2025/10/07/analysing-the-state-of-happy-eyeballs-implementations concludes with the observation "that slow A queries also slow down IPv6, even when IPv6 is not the cause of slower responses. This may contribute to negative perceptions of IPv6 and adversely affect IPv6 deployment."
Analysing the state of Happy Eyeballs implementations | APNIC Blog
Guest Post: The Happy Eyeballs algorithm supports IPv6 deployment by giving clients the ability to prefer IPv6, quickly fall back to IPv4 when necessary, and protect the user experience in either case. But how widely is it implemented?
Jörn FrankeAt APNIC 60, during the IPv6 Deployment session, several presentations explored the state of IPv6 research, deployment, and adoption — from scanning techniques and national transition strategies to operational rollouts. Together, they highlighted how IPv6 continues to evolve across research, policy, and practice, with a clear shift towards IPv6-only. This post explores those presentations.
https://blog.apnic.net/2025/09/18/ipv6-deployment-at-apnic-60/
