aboutsummaryrefslogtreecommitdiffstats
path: root/chapter09/networkd.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter09/networkd.xml')
-rw-r--r--chapter09/networkd.xml12
1 files changed, 9 insertions, 3 deletions
diff --git a/chapter09/networkd.xml b/chapter09/networkd.xml
index 82a0740ad..42c7dc730 100644
--- a/chapter09/networkd.xml
+++ b/chapter09/networkd.xml
@@ -184,15 +184,21 @@ EOF</userinput></screen>
or any other software that generates an <filename>/etc/resolv.conf</filename>
(ex: a <command>resolvconf</command> program other than the one
provided by systemd), the <command>systemd-resolved</command> service
- should not be used.</para></note>
+ should not be used.</para>
+
+ <para>To disable systemd-resolved, issue the following command:</para>
+
+<screen role="nodump"><userinput>systemctl disable systemd-resolved</userinput></screen></note>
<para>When using <command>systemd-resolved</command> for DNS
configuration, it creates the file
- <filename>/run/systemd/resolve/resolv.conf</filename>. Create a
+ <filename>/run/systemd/resolve/resolv.conf</filename>.</para>
+ <!--Create a
symlink in <filename>/etc</filename> to use the generated file:</para>
<screen><userinput>ln -sfv /run/systemd/resolve/resolv.conf /etc/resolv.conf</userinput></screen>
-
+ At least in systemd-250, this file gets created on first bootup.
+ -->
</sect3>
<sect3 id="resolv-conf-static">