Unbound / systemd-resolved

[KatyComputer]

I have my PVE box configuring using the Routed configuration. Everything was going well until I decided to install Unbound on eno1. Curiously, I had no trouble running PowerDNS Recursor on eno1.

Unbound wouldn't start, I did some digging and learned systemd-resolved was listening on port 53, so I executed systemctl disable systemd-resolved --now, this allowed unbound to start, but caused eno1 to stop routing packets to vmbr0

Urgh #@@%@#!!

After several hours of research, found the solution, I edited /etc/systemd/resolved.conf:
[Resolve]
DNS=127.0.0.1
FallbackDNS=1.0.0.1
MulticastDNS=no
DNSStubListener=no

Then ran: systemctl enable systemd-resolved --now

All is now well. Anyone know why systemd-resolved is required for routing, or why everything works fine with pdns? In any event, I hope this helps someone.

 

[t.lamprecht]

All is now well. Anyone know why systemd-resolved is required for routing, or why everything works fine with pdns? In any event, I hope this helps someone.

It shouldn't be, also here I do not use systemd-resolved at all:

systemctl status systemd-resolved.service 
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-resolved.service.d
           └─resolvconf.conf
   Active: inactive (dead)

So something else pulled it in...

 

[KatyComputer]

We have a mystery. I ran

systemctl disable systemd-resolved --now
reboot

Everything is working. I am not sure why things failed last week-end. Thanks for looking into this for me.