EDIT: 22.04.2
Hi all,
I took into account and followed the guide here: GitHub - pi-hole/docker-pi-hole: Pi-hole in a docker container.
I kept systemd/resolvd
running - with the stub listener disabled and the symlink provided in the guide.
I am now managing my /etc/resolv.conf
with netplan
as per the guide but my host machine is now no longer to resolve any names/DNS not configured correctly. I've shown any relevant files below.
Hopefully someone can point out a mistake I've made that can get me back up and running - or at least point out where to look/how I can reverse the changes I made following the guide mentioned?
Any help most appreciated.
Single config in /etc/netplan
network:
version: 2
renderer: networkd
ethernets:
enp4s0:
addresses:
- [redacted]/32
routes:
- on-link: true
to: 0.0.0.0/0
via: [redacted]
- to: default
via: [redacted]
nameservers:
addresses:
- 1.1.1.1
- 1.0.0.1
/etc/resolv.conf
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# 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 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.
nameserver 1.1.1.1
nameserver 1.1.1.1
nameserver 1.0.0.1
search .