<?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>chs.us — Carl Sampson</title><link>https://chs.us/</link><description/><language>en-us</language><managingEditor>carl.sampson@gmail.com (Carl Sampson)</managingEditor><webMaster>carl.sampson@gmail.com (Carl Sampson)</webMaster><lastBuildDate>Wed, 08 Jul 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://chs.us/tags/dnslib/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an authoritative DNS server in ~200 lines</title><link>https://chs.us/2026/07/authoritative-dns-from-scratch/</link><pubDate>Wed, 08 Jul 2026 12:00:00 +0000</pubDate><author>carl.sampson@gmail.com (Carl Sampson)</author><guid>https://chs.us/2026/07/authoritative-dns-from-scratch/</guid><description>An OAST platform needs to own a zone and answer anything under it. Here&amp;#39;s a from-scratch authoritative DNS server — wildcards, apex records, deliverable MX, and answering your own ACME challenges — and the protocol subtleties that bite.</description><category>Security</category><category>Dns</category><category>Networking</category><category>Oast</category><category>Python</category><category>Dnslib</category><category>Infrastructure</category></item></channel></rss>