<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;">
<p dir="auto">On 10 May 2025, at 4:29, <a href="mailto:bind9@clearviz.biz" style="color: #3983C4;">bind9@clearviz.biz</a> wrote:</p>
<blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;">
<p dir="auto">The resolv.conf file contains:</p>
<pre style="margin-left: 15px; margin-right: 15px; padding: 5px; background-color: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; max-width: 90vw;"><code style="margin: 0 0; border-radius: 3px; background-color: #F7F7F7; padding: 0px;"> nameserver 127.0.0.53
search mydomain.net
</code></pre>
</blockquote>
<p dir="auto">On a "vanilla" Ubuntu system, the file to which <em>/etc/resolv.conf</em><br>
is a symlink contains (in addition to the above) relevant comments,<br>
including the following.</p>
<pre style="margin-left: 15px; margin-right: 15px; padding: 5px; background-color: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; max-width: 90vw;"><code style="margin: 0 0; border-radius: 3px; background-color: #F7F7F7; padding: 0px;"># Third party programs should typically 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.
</code></pre>
<p dir="auto">What I do, is to create a file with a name which I hope will<br>
be safe from future interfering Ubuntu updates and set it up to<br>
refer to my actual nameserver addresses, rename <em>resolv.conf</em><br>
(the symlink) to something harmless (or so I hope), and copy<br>
my "safe" file as <em>/etc/resolv.conf</em>, with the results shown below.</p>
<pre style="margin-left: 15px; margin-right: 15px; padding: 5px; background-color: #F7F7F7; border-radius: 5px 5px 5px 5px; overflow-x: auto; max-width: 90vw;"><code style="margin: 0 0; border-radius: 3px; background-color: #F7F7F7; padding: 0px;">turf(p84)11: ls -l /etc/resolv.conf*
-rw-r--r-- 1 root root 155 Nov 23 16:22 /etc/resolv.conf
lrwxrwxrwx 1 root root 39 Sep 28 2024 /etc/resolv.conf-original -> ../run/systemd/resolve/stub-resolv.conf
-rw-r--r-- 1 root root 155 Nov 23 16:21 /etc/resolv.conf-tailored
turf(p84)12: diff -qs /etc/resolv.conf{,-tailored}
Files /etc/resolv.conf and /etc/resolv.conf-tailored are identical
turf(p84)12:
</code></pre>
<p dir="auto">It seems that I never bothered to disable the systemd-resolved<br>
service. I don't recall whether I gave up trying, or just couldn't<br>
be arsed to work out how.</p>
<p dir="auto">IMHO, systemd is an abomination, but it's easier to go with the<br>
flow than to eliminate it.</p>
<p dir="auto">I hope this helps.</p>
<p dir="auto">/Niall</p>
</div>
</div>
</body>
</html>