<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Coredns on Compile My Mind</title>
		<link>https://www.compilemymind.com/tags/coredns/</link>
		<description>Recent content in Coredns on Compile My Mind</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Sun, 26 Jul 2026 19:00:00 +0200</lastBuildDate>
		
			<atom:link href="https://www.compilemymind.com/tags/coredns/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Troubleshoot Kubernetes DNS Resolution from Pods</title>
				<link>https://www.compilemymind.com/posts/troubleshoot-kubernetes-dns-resolution-pods/</link>
				<pubDate>Tue, 21 Jul 2026 17:25:18 +0300</pubDate>
				<guid>https://www.compilemymind.com/posts/troubleshoot-kubernetes-dns-resolution-pods/</guid>
				<description>&lt;p&gt;“The pod cannot reach &lt;code&gt;orders&lt;/code&gt;” describes at least four different failures:&lt;/p&gt;&#xA;&lt;ol&gt;&#xA;&lt;li&gt;The pod generated a different DNS query than expected.&lt;/li&gt;&#xA;&lt;li&gt;Cluster DNS did not answer correctly.&lt;/li&gt;&#xA;&lt;li&gt;DNS resolved, but the Service virtual IP was unreachable.&lt;/li&gt;&#xA;&lt;li&gt;The Service was reachable, but no healthy backend served the request.&lt;/li&gt;&#xA;&lt;/ol&gt;&#xA;&lt;p&gt;Changing CoreDNS before locating the failing layer usually adds noise. Start inside the affected pod or namespace and move outward one boundary at a time.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
