<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>/Etc/Resolv.conf on </title>
    <link>https://wassimaouadi.com/tags/etc/resolv.conf/</link>
    <description>Recent content in /Etc/Resolv.conf on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Jul 2026 21:31:13 +0200</lastBuildDate>
    <atom:link href="https://wassimaouadi.com/tags/etc/resolv.conf/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Domain Name Resolution</title>
      <link>https://wassimaouadi.com/posts/nameresolution/</link>
      <pubDate>Wed, 29 Jul 2026 21:31:13 +0200</pubDate>
      <guid>https://wassimaouadi.com/posts/nameresolution/</guid>
      <description>&lt;h1 id=&#34;name-resolution-in-linux&#34;&gt;name resolution in Linux&lt;/h1&gt;&#xA;&lt;p&gt;Name resolution in Linux is a pipeline of verification jobs, not a single file: a process consults the Name Service Switch, which has a configuration file at &lt;em&gt;/etc/nsswitchconf&lt;/em&gt;. This file contains a list of entries. Each entry describes a database and the list of sources to refer to in the order of their appearance in the entry.&lt;/p&gt;&#xA;&lt;p&gt;An entry is written in this format: &lt;strong&gt;&lt;em&gt;DatabaseName NameService1 [Status=Action] NameService2&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
