<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>mb on Ritesh Sonawane</title><link>https://riteshsonawane.com/tags/mb/</link><description>Recent content in mb on Ritesh Sonawane</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 07 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://riteshsonawane.com/tags/mb/index.xml" rel="self" type="application/rss+xml"/><item><title>ndots in Kubernetes</title><link>https://riteshsonawane.com/blog/ndots-in-kubernetes/</link><pubDate>Tue, 07 Apr 2026 00:00:00 +0000</pubDate><guid>https://riteshsonawane.com/blog/ndots-in-kubernetes/</guid><description>&lt;p&gt;Let&amp;rsquo;s see how the &lt;code&gt;ndots&lt;/code&gt; option works in Kubernetes.&lt;/p&gt;
&lt;p&gt;In Kubernetes, we connect to running pods either directly or via a Kubernetes Service. This post focuses on how service DNS resolution actually works under the hood.&lt;/p&gt;
&lt;h2 id="the-resolvconf-file"&gt;The resolv.conf file&lt;/h2&gt;
&lt;p&gt;In Linux, &lt;code&gt;/etc/resolv.conf&lt;/code&gt; is used by the &lt;a href="https://man7.org/linux/man-pages/man3/resolver.3.html"&gt;system resolver&lt;/a&gt; for domain name resolution. Kubernetes automatically injects this file into every pod with the configuration needed to resolve services inside the cluster.&lt;/p&gt;
&lt;p&gt;Here is an example from a CNPG cluster pod running in the &lt;code&gt;database&lt;/code&gt; namespace:&lt;/p&gt;</description></item></channel></rss>