<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Post-Mortems</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Post-Mortems feed</description>
    <item>
      <title>How CNAME Ordering in RFC Specs Caused Cloudflare 1.1.1.1 Outage</title>
      <link>https://www.infoq.com/news/2026/02/cname-rfc-cloudflare-outage/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Post-Mortems</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/02/cname-rfc-cloudflare-outage/en/headerimage/generatedHeaderImage-1769435290840.jpg"/&gt;&lt;p&gt;In a recent article titled "What came first- the CNAME or the A record?" Cloudflare explains how an unclear RFC specification caused the popular Cloudflare’s 1.1.1.1 service to break. After identifying the breakage and the ambiguity in older DNS standards regarding record order, Cloudflare proposes a clarified specification.&lt;/p&gt; &lt;i&gt;By Renato Losio&lt;/i&gt;</description>
      <category>Network Programming</category>
      <category>Infrastructure</category>
      <category>Networking</category>
      <category>DNS</category>
      <category>Post-Mortems</category>
      <category>Cloudflare</category>
      <category>Incident Response</category>
      <category>IETF</category>
      <category>DevOps</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Sat, 07 Feb 2026 11:32:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/02/cname-rfc-cloudflare-outage/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Post-Mortems</guid>
      <dc:creator>Renato Losio</dc:creator>
      <dc:date>2026-02-07T11:32:00Z</dc:date>
      <dc:identifier>/news/2026/02/cname-rfc-cloudflare-outage/en</dc:identifier>
    </item>
  </channel>
</rss>
