<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Setup Local DNS Using /etc/hosts File in Linux	</title>
	<atom:link href="https://www.tecmint.com/setup-local-dns-using-etc-hosts-file-in-linux/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/setup-local-dns-using-etc-hosts-file-in-linux/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Wed, 04 Mar 2020 19:40:22 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Serviceyards.Com		</title>
		<link>https://www.tecmint.com/setup-local-dns-using-etc-hosts-file-in-linux/comment-page-1/#comment-1320018</link>

		<dc:creator><![CDATA[Serviceyards.Com]]></dc:creator>
		<pubDate>Wed, 04 Mar 2020 19:40:22 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=26426#comment-1320018</guid>

					<description><![CDATA[Linux does provide the bind RPM package to allow an administrative domain to configure and maintain its own DNS service, but frequently the size of the local network is only a few hosts and makes justifying the effort of maintaining a DNS service unwarranted.]]></description>
			<content:encoded><![CDATA[<p>Linux does provide the bind RPM package to allow an administrative domain to configure and maintain its own DNS service, but frequently the size of the local network is only a few hosts and makes justifying the effort of maintaining a DNS service unwarranted.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joerg Lerche		</title>
		<link>https://www.tecmint.com/setup-local-dns-using-etc-hosts-file-in-linux/comment-page-1/#comment-1302907</link>

		<dc:creator><![CDATA[Joerg Lerche]]></dc:creator>
		<pubDate>Fri, 06 Dec 2019 16:47:10 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=26426#comment-1302907</guid>

					<description><![CDATA[Please refer to &lt;code&gt;https://unix.stackexchange.com/questions/421491/what-is-the-purpose-of-etc-hosts&lt;/code&gt;.]]></description>
			<content:encoded><![CDATA[<p>Please refer to <code>https://unix.stackexchange.com/questions/421491/what-is-the-purpose-of-etc-hosts</code>.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Joerg Lerche		</title>
		<link>https://www.tecmint.com/setup-local-dns-using-etc-hosts-file-in-linux/comment-page-1/#comment-1302886</link>

		<dc:creator><![CDATA[Joerg Lerche]]></dc:creator>
		<pubDate>Fri, 06 Dec 2019 16:10:02 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=26426#comment-1302886</guid>

					<description><![CDATA[Hello Aaron,

I&#039;m sad to say that in above article you did not describe DNS at all. You instead described how to configure local name resolution on a Linux host through &lt;strong&gt;/etc/hosts&lt;/strong&gt;. In this scenario, DNS is not involved at all. 

Think of OS name resolution like an umbrella. In &lt;strong&gt;nsswitch.conf&lt;/strong&gt; the sysadmin configures what name resolution services for this system should be. Files usually come first (means &lt;strong&gt;/etc/hosts&lt;/strong&gt;), DNS is one of them - it usually follows files but there are a lot more different name resolution services and strategies available.

&quot;&lt;strong&gt;getent hosts &lt;/strong&gt;&quot; query the OS to resolve  according to configured name resolution services in that order (and usually checks &lt;strong&gt;/etc/hosts&lt;/strong&gt; firsts and then maybe DNS, but always does what&#039;s written in &lt;strong&gt;nsswitch.conf&lt;/strong&gt; behind &quot;hosts:&quot;)

&quot;&lt;strong&gt;host&lt;/strong&gt;&quot; explicitly asks DNS service to resolve. This won&#039;t resolve hostnames that only &lt;strong&gt;/etc/hosts&lt;/strong&gt; can resolve - to demonstrate the difference.


Please read the man pages of &quot;&lt;strong&gt;getent&lt;/strong&gt;&quot; and &quot;&lt;strong&gt;hosts&lt;/strong&gt;&quot;.

I suggest completely overhaul this article or take it off-line.

Greetings,
Joerg]]></description>
			<content:encoded><![CDATA[<p>Hello Aaron,</p>
<p>I&#8217;m sad to say that in above article you did not describe DNS at all. You instead described how to configure local name resolution on a Linux host through <strong>/etc/hosts</strong>. In this scenario, DNS is not involved at all. </p>
<p>Think of OS name resolution like an umbrella. In <strong>nsswitch.conf</strong> the sysadmin configures what name resolution services for this system should be. Files usually come first (means <strong>/etc/hosts</strong>), DNS is one of them &#8211; it usually follows files but there are a lot more different name resolution services and strategies available.</p>
<p>&#8220;<strong>getent hosts </strong>&#8221; query the OS to resolve  according to configured name resolution services in that order (and usually checks <strong>/etc/hosts</strong> firsts and then maybe DNS, but always does what&#8217;s written in <strong>nsswitch.conf</strong> behind &#8220;hosts:&#8221;)</p>
<p>&#8220;<strong>host</strong>&#8221; explicitly asks DNS service to resolve. This won&#8217;t resolve hostnames that only <strong>/etc/hosts</strong> can resolve &#8211; to demonstrate the difference.</p>
<p>Please read the man pages of &#8220;<strong>getent</strong>&#8221; and &#8220;<strong>hosts</strong>&#8220;.</p>
<p>I suggest completely overhaul this article or take it off-line.</p>
<p>Greetings,<br />
Joerg</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
