My Introduction and current issues -

[Niall O'Reilly]

On 10 May 2025, at 4:29, bind9 at clearviz.biz wrote:

> The resolv.conf file contains:
>
>       nameserver 127.0.0.53
>       search mydomain.net

On a "vanilla" Ubuntu system, the file to which */etc/resolv.conf*
is a symlink contains (in addition to the above) relevant comments,
including the following.

```
# 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.
```

What I do, is to create a file with a name which I hope will
be safe from future interfering Ubuntu updates and set it up to
refer to my actual nameserver addresses, rename *resolv.conf*
(the symlink) to something harmless (or so I hope), and copy
my "safe" file as */etc/resolv.conf*, with the results shown below.

```
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:
```

It seems that I never bothered to disable the systemd-resolved
service. I don't recall whether I gave up trying, or just couldn't
be arsed to work out how.

IMHO, systemd is an abomination, but it's easier to go with the
flow than to eliminate it.

I hope this helps.

/Niall
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20250510/41ea359c/attachment.htm>