Building resilient self hosted services is not always easy
Resiliency through more redundancy is important no matter the scenario.
Resiliency through more redundancy is important no matter the scenario.
APNIC welcomes you to Mumbai, India for APNIC 62. Here is what you can look forward to over the coming days.
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.
An analysis of the traffic impacts of locally served root zones, by Ilyas Rahimi at UvA.
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.
Guest Post: The recent Telstra outage highlighted a critical but often overlooked dependency in modern networks: Accurate time synchronization.
Guest Post: Patching faster cannot keep up with AI-driven discovery. Leverage structural invariants to make bug classes irrelevant.
Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53.
A growing debate within the IETF is exploring how AI-generated content should be used and disclosed in standards discussions.
Guest Post: RPKI has made real progress against prefix hijacking. But when you map every known class of BGP attack against the defences that exist, four of them turn out to sit entirely outside cryptographic validation — handled with local filters, static thresholds and reactive response.