
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>AzureFixes</title>
      <link>https://Azurefixes.com/blog</link>
      <description>This blog is for Azure Troubleshooting</description>
      <language>en-us</language>
      <managingEditor>address@yoursite.com (NVN)</managingEditor>
      <webMaster>address@yoursite.com (NVN)</webMaster>
      <lastBuildDate>Thu, 18 Jun 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://Azurefixes.com/tags/coredns/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://Azurefixes.com/blog/kubernetes-dns-failures</guid>
    <title>Diagnosing Kubernetes DNS Resolution Failures: CoreDNS Upstream Forwarding Broken by resolv.conf Drift</title>
    <link>https://Azurefixes.com/blog/kubernetes-dns-failures</link>
    <description>If some pods in your AKS cluster resolve external DNS names fine and others fail — from the same Deployment, same image, same config — the variable is the node. This guide covers the exact test sequence to isolate CoreDNS upstream forwarding failures, identify /etc/resolv.conf drift on worker nodes, and fix it without reprovisioning.</description>
    <pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate>
    <author>address@yoursite.com (NVN)</author>
    <category>Kubernetes</category><category>AKS</category><category>CoreDNS</category><category>DNS</category><category>Troubleshooting</category><category>Networking</category>
  </item>

    </channel>
  </rss>
