<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>BIND9 on Netacoding | Cybersecurity, Assembly &amp; Network Research</title>
    <link>https://netacoding.com/tags/bind9/</link>
    <description>Recent content in BIND9 on Netacoding | Cybersecurity, Assembly &amp; Network Research</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 11 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://netacoding.com/tags/bind9/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DNS State Exhaustion: From TCP Slot Starvation to NXNS Amplification</title>
      <link>https://netacoding.com/posts/dns-state-exhaustion/</link>
      <pubDate>Mon, 11 May 2026 00:00:00 +0000</pubDate>
      <guid>https://netacoding.com/posts/dns-state-exhaustion/</guid>
      <description>DNS is often described as a stateless UDP protocol. In practice every recursive resolver carries substantial per-query state, and that state has surprisingly low default ceilings. This post is a thorough walk through the state that DNS resolvers hold, the attack families that target it, and why DNS defaults are often lower than HTTP defaults.</description>
    </item>
  </channel>
</rss>
