Differences

This shows you the differences between two versions of the page.

--- ubuntu:networking:dns:etc_resolv.conf [2021/01/10 21:03] – [Common DNS configuration changes] peter
+++ ubuntu:networking:dns:etc_resolv.conf [2021/01/13 11:05] (current) – [Display /etc/resolv.conf] peter
@@ Line 7: / Line 7: @@
   * **/etc/resolv.conf** is nowadays maintained by systemd.
   * If DNS resolver changes are needed then do this through systemd.
+</WRAP>
+----
+===== List /etc/resolv.conf =====
+<code bash>
+ls -al /etc/resolv.conf
+</code>
+returns:
+<code bash>
+lrwxrwxrwx 1 root root 32 Jan 10 18:50 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf
+</code>
+<WRAP info>
+**NOTE:**  This shows that **/etc/resolv.conf** is a symlink to **/run/systemd/resolve/resolv.conf**.
+It may instead be a symlink to **/run/systemd/resolve/stub-resolv.conf**.  Also ok.
+If not then to fix try:
+<code bash>
+sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
+</code>
+</WRAP>
+----
+===== Display /etc/resolv.conf =====
+<code bash>
+cat /etc/resolv.conf
+</code>
+returns:
+<code bash>
+# This file is managed by man:systemd-resolved(8). Do not edit.
+#
+# This is a dynamic resolv.conf file for connecting local clients directly to
+# all known uplink DNS servers. This file lists all configured search domains.
+#
+# Third party programs must not access this file directly, but only through the
+# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
+# replace this symlink by a static file or a different symlink.
+#
+# See man:systemd-resolved.service(8) for details about the supported modes of
+# operation for /etc/resolv.conf.
+nameserver 192.168.1.1
+search localdomain
+</code>
+<WRAP info>
+**NOTE:**  If the **nameserver** is **127.0.0.53** then this is fine too - It is set as default by Ubuntu.
+Usually it would only show as 192.168.1.1 or similar if DNS changes had been made in networking settings; such as in /etc/netplan.
 </WRAP>