<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dns on Kuldeep Pisda</title><link>https://kdpisda.in/tag/dns/</link><description>Recent content in Dns on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 23 Oct 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>Control D's Bad Setting Sat Dormant for 25 Days, Then a Fail-Closed Startup Check Turned One Reload Into a Fleet-Wide Outage</title><link>https://kdpisda.in/controld-dns-outage-integer-override/</link><pubDate>Fri, 23 Oct 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/controld-dns-outage-integer-override/</guid><description>&lt;p&gt;Control D&amp;rsquo;s paid DNS stopped answering queries at every location for 55 minutes on October 11, 2026. The &lt;a href="https://controld.com/blog/incident-october-11-2026/"&gt;postmortem&lt;/a&gt;, published October 20, puts the cause in a change that had shipped 25 days earlier and had not done anything since.&lt;/p&gt;
&lt;p&gt;The shape of the failure is worth separating into three independent defects, because each one has a different fix and a different place in your own systems where it could be hiding.&lt;/p&gt;</description></item></channel></rss>