On 4/20/19 3:36 AM, Pierre Labastie via blfs-support wrote:
Writing to -support, because I am very newbie to systemd.
On the systemd book, both for bind and unbound, there is an instruction to
modify the /etc/resolv.conf file, such as:
# unbound
echo "nameserver 127.0.0.1" > /etc/resolv.conf
# bind
cat > /etc/resolv.conf << "EOF"
search <yourdomain.com>
nameserver 127.0.0.1
EOF
But if /etc/resolv.conf is a symlink (as advised in the LFS book), this will
write to the symlinked file, not recreate /etc/resolv.conf as a regular file.
So I think those settings would be lost at next reboot...
Also, it is advised to do:
# bind
systemctl start named
but not for unbound.
Shouldn't systemd-resolved be stopped and disabled first?
And actually, isn't systemd-resolved enough, and do we need bind or unbound?
I'm not that familiar with systemd-resolved or unbound, but I think both
are just dns clients similar to dhcpcd. bind has a robust server and a
client. We provide a configuration for the bind server that allows
using it as a local caching name server, but it can be configured as a
robust internet name server.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
