<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Dns on The IT Hollow</title>
    <link>https://theithollow.com/tags/dns/</link>
    <description>Recent content in Dns on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 Feb 2019 15:00:16 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/dns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kubernetes - DNS</title>
      <link>https://theithollow.com/2019/02/18/kubernetes-dns/</link>
      <pubDate>Mon, 18 Feb 2019 15:00:16 +0000</pubDate>
      <guid>https://theithollow.com/2019/02/18/kubernetes-dns/</guid>
      <description>&lt;p&gt;DNS is a critical service in any system. Kubernetes is no different, but Kubernetes will implement its own domain naming system that&amp;rsquo;s implemented within your Kubernetes cluster. This post explores the details that you need to know to operate a k8s cluster properly.&lt;/p&gt;
&lt;h2 id=&#34;kubernetes-dns---the-theory&#34;&gt;Kubernetes DNS - The theory&lt;/h2&gt;
&lt;p&gt;I don&amp;rsquo;t want to dive into DNS too much since it&amp;rsquo;s a core service most should be familiar with. But at a really high level, DNS translates an IP address that might be changing, with an easily remember-able name such as &amp;ldquo;theithollow.com&amp;rdquo;. Every network has a DNS server, but Kubernetes implements their own DNS within the cluster to make connecting to containers a simple task.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
