<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>CoreDNS - Tag - vo.rs</title><link>https://vo.rs/tags/coredns/</link><description>CoreDNS - Tag - vo.rs</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright><lastBuildDate>Tue, 30 Jul 2024 09:00:00 +0000</lastBuildDate><atom:link href="https://vo.rs/tags/coredns/" rel="self" type="application/rss+xml"/><item><title>CoreDNS and Kubernetes DNS: What Actually Happens When a Pod Looks Up a Name</title><link>https://vo.rs/story/coredns-and-kubernetes-dns-what-actually-happens-when-a-pod-looks-up-a-name/</link><description>&lt;p&gt;For something so fundamental, Kubernetes DNS is astonishingly easy to take for granted. You write &lt;code&gt;http://my-service&lt;/code&gt; in your code, it resolves, traffic flows, everyone goes home. Then one day a pod can&amp;rsquo;t reach another service, &lt;code&gt;nslookup&lt;/code&gt; returns SERVFAIL, and you discover you have no idea what was happening under the hood the entire time. I have been that person at 1am, and I would rather you weren&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;So let&amp;rsquo;s follow a single DNS lookup end to end. No magic, just a chain of unremarkable Linux mechanics that happen to be wired together rather cleverly.&lt;/p&gt;</description><pubDate>Tue, 30 Jul 2024 09:00:00 +0000</pubDate></item></channel></rss>