man/resolved.conf.d.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>resolved.conf</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><style>
   2     a.headerlink {
   3       color: #c60f0f;
   4       font-size: 0.8em;
   5       padding: 0 4px 0 4px;
   6       text-decoration: none;
   7       visibility: hidden;
   8     }
   9
  10     a.headerlink:hover {
  11       background-color: #c60f0f;
  12       color: white;
  13     }
  14
  15     h1:hover > a.headerlink, h2:hover > a.headerlink, h3:hover > a.headerlink, dt:hover > a.headerlink {
  16       visibility: visible;
  17     }
  18   </style><a href="index.html">Index </a>·
  19   <a href="systemd.directives.html">Directives </a>·
  20   <a href="../python-systemd/index.html">Python </a>·
  21   <a href="../libudev/index.html">libudev </a>·
  22   <a href="../libudev/index.html">gudev </a><span style="float:right">systemd 219</span><hr><div class="refentry"><a name="resolved.conf"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>resolved.conf, resolved.conf.d — Network Name Resolution configuration files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><code class="filename">/etc/systemd/resolved.conf</code></p><p><code class="filename">/etc/systemd/resolved.conf.d/*.conf</code></p><p><code class="filename">/run/systemd/resolved.conf.d/*.conf</code></p><p><code class="filename">/usr/lib/systemd/resolved.conf.d/*.conf</code></p></div><div class="refsect1"><a name="idm140621226599024"></a><h2 id="Description">Description<a class="headerlink" title="Permalink to this headline" href="#Description">¶</a></h2><p>These configuration files control local DNS and LLMNR
  23     name resolving.</p></div><div class="refsection"><a name="confd"></a><h2>Configuration Directories and Precedence</h2><p>Configuration files are read from directories in
  24     <code class="filename">/etc/</code>, <code class="filename">/run/</code>, and
  25     <code class="filename">/usr/lib/</code>, in order of precedence.
  26     Each configuration file in these configuration directories shall be named in
  27     the style of <code class="filename"><em class="replaceable"><code>filename</code></em>.conf</code>.
  28     Files in <code class="filename">/etc/</code> override files with the same name in
  29     <code class="filename">/run/</code> and <code class="filename">/usr/lib/</code>. Files in
  30     <code class="filename">/run/</code> override files with the same name in
  31     <code class="filename">/usr/lib/</code>.</p><p>Packages should install their configuration files in
  32     <code class="filename">/usr/lib/</code>. Files in <code class="filename">/etc/</code> are
  33     reserved for the local administrator, who may use this logic to override the
  34     configuration files installed by vendor packages. All configuration files
  35     are sorted by their filename in lexicographic order, regardless of which of
  36     the directories they reside in. If multiple files specify the same option,
  37     the entry in the file with the lexicographically latest name will take
  38     precedence. It is recommended to prefix all filenames with a two-digit number
  39     and a dash, to simplify the ordering of the files.</p><p>If the administrator wants to disable a configuration file supplied by
  40     the vendor, the recommended way is to place a symlink to
  41     <code class="filename">/dev/null</code> in the configuration directory in
  42     <code class="filename">/etc/</code>, with the same filename as the vendor
  43     configuration file.</p></div><div class="refsection"><a name="conf"></a><h2>Configuration File</h2><p>Configuration is also read from a single configuration file in
  44     <code class="filename">/etc/</code>. This file is read before any of the
  45     configuration directories, and has the lowest precedence; entries in a file
  46     in any configuration directory override entries in the single configuration
  47     file.</p></div><div class="refsect1"><a name="idm140621226596192"></a><h2 id="Options">Options<a class="headerlink" title="Permalink to this headline" href="#Options">¶</a></h2><div class="variablelist"><dl class="variablelist"><dt id="DNS="><span class="term"><code class="varname">DNS=</code></span><a class="headerlink" title="Permalink to this term" href="#DNS=">¶</a></dt><dd><p>A space separated list of IPv4 and IPv6
  48         addresses to be used as system DNS servers. DNS requests are
  49         sent to one of the listed DNS servers in parallel to any
  50         per-interface DNS servers acquired from
  51         <a href="systemd-networkd.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-networkd.service</span>(8)</span></a>.
  52         For compatibility reasons, if set to the empty list the DNS
  53         servers listed in <code class="filename">/etc/resolv.conf</code> are
  54         used, if any are configured there. This setting defaults to
  55         the empty list.</p></dd><dt id="FallbackDNS="><span class="term"><code class="varname">FallbackDNS=</code></span><a class="headerlink" title="Permalink to this term" href="#FallbackDNS=">¶</a></dt><dd><p>A space separated list of IPv4 and IPv6
  56         addresses to be used as the fallback DNS servers. Any
  57         per-interface DNS servers obtained from
  58         <a href="systemd-networkd.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-networkd.service</span>(8)</span></a>
  59         take precedence over this setting, as do any servers set via
  60         <code class="varname">DNS=</code> above or
  61         <code class="filename">/etc/resolv.conf</code>. This setting is hence
  62         only used if no other DNS server information is known. If this
  63         option is not given, a compiled-in list of DNS servers is used
  64         instead.</p></dd><dt id="LLMNR="><span class="term"><code class="varname">LLMNR=</code></span><a class="headerlink" title="Permalink to this term" href="#LLMNR=">¶</a></dt><dd><p>Takes a boolean argument or
  65         "<code class="literal">resolve</code>". Controls Link-Local Multicast Name
  66         Resolution support (<a class="ulink" href="https://tools.ietf.org/html/rfc4795" target="_top">RFC 4794</a>) on
  67         the local host. If true enables full LLMNR responder and
  68         resolver support. If false disable both. If set to
  69         "<code class="literal">resolve</code>" only resolving support is enabled,
  70         but responding is disabled. Note that
  71         <a href="systemd-networkd.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-networkd.service</span>(8)</span></a>
  72         also maintains per-interface LLMNR settings. LLMNR will be
  73         enabled on an interface only if the per-interface and the
  74         global setting is on.</p></dd></dl></div></div><div class="refsect1"><a name="idm140621226659056"></a><h2 id="See Also">See Also<a class="headerlink" title="Permalink to this headline" href="#See%20Also">¶</a></h2><p>
  75       <a href="systemd.html"><span class="citerefentry"><span class="refentrytitle">systemd</span>(1)</span></a>,
  76       <a href="systemd-resolved.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-resolved.service</span>(8)</span></a>,
  77       <a href="systemd-networkd.service.html"><span class="citerefentry"><span class="refentrytitle">systemd-networkd.service</span>(8)</span></a>,
  78       <a href="http://man7.org/linux/man-pages/man4/resolv.conf.4.html"><span class="citerefentry"><span class="refentrytitle">resolv.conf</span>(4)</span></a>
  79       </p></div></div></body></html>