[Podcast] ‘Just say no’ isn’t as simple as you think
A continuation of the discussion on surplus DNS queries seen at APNIC Labs, the implications of how you say ‘no’, and the transport used for the DNS
Category:
Tech matters
The case for open-weight models and why we can’t trust frontier labs
Guest Post: A frontier API can refuse, change, or vanish out from under you. Open weights keep the model you depend on yours.
One or two nameservers?
Do multiple dual-stack nameservers increase or decrease repeat DNS queries? The results of this experiment were a complete surprise.
Building resilient self hosted services is not always easy
Resiliency through more redundancy is important no matter the scenario.
Welcome to APNIC 62
APNIC welcomes you to Mumbai, India for APNIC 62. Here is what you can look forward to over the coming days.
What part of ‘No!’ is so hard for the DNS to understand?
At APNIC Labs we’ve been experimenting with understanding how the DNS handles requests to resolve nonexistent names to make the DNS more resilient to random name attacks.
[Podcast] Measuring the impact of locally served root zone
An analysis of the traffic impacts of locally served root zones, by Ilyas Rahimi at UvA.
Beeline: Enforcing application-layer policies in eBPF
Guest Post: While many L7 protocols are complex to parse, the logic needed to enforce L7 policies tends to be simple. For the vast majority (89%) of L7 policies in the wild, Beeline can eliminate the service proxy from the critical path.
The invisible heartbeat of our networks
Guest Post: The recent Telstra outage highlighted a critical but often overlooked dependency in modern networks: Accurate time synchronization.
The day after the zero-days
Guest Post: Patching faster cannot keep up with AI-driven discovery. Leverage structural invariants to make bug classes irrelevant.