<?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>Bind on Damien Dye&#39;s Blog</title>
    <link>https://blogs.damiendye.uk/en/tags/bind/</link>
    <description>Recent content in Bind on Damien Dye&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-GB</language>
    <lastBuildDate>Mon, 24 Aug 2026 09:00:00 +0100</lastBuildDate>
    <atom:link href="https://blogs.damiendye.uk/en/tags/bind/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Samba4 and Securing AD Records Using DNSSEC</title>
      <link>https://blogs.damiendye.uk/en/dns/samba4-securing-ad-records-with-dnssec/</link>
      <pubDate>Mon, 24 Aug 2026 09:00:00 +0100</pubDate>
      <guid>https://blogs.damiendye.uk/en/dns/samba4-securing-ad-records-with-dnssec/</guid>
      <description>Every domain-joined machine finds its DC by asking DNS for an SRV record, so the _msdcs locators are the most security-critical records you have. Signing them from a Samba4 DC: BIND with dlz_bind9, inline signing, a hidden primary, dynamic updates kept out of the locator zone, then forcing Windows and Linux clients to validate the signatures.</description>
    </item>
  </channel>
</rss>
