Open Ninlives opened 2 years ago
/etc/resolv.conf is read once on server startup, might it be that /etc/resolv.conf does not exist (or is not populated correctly) when maddy starts? In that case you would need to adjust the systemd unit file to ensure it starts after the correct configuration is generated.
Sure, I add another service that restart maddy everytime /etc/resolv.conf is changed, it works, but tricky.
Describe the bug
I set up a maddy service on a Vultr VPS, and it seems maddy does not respect the nameserver settings in
/etc/resolve.conf
and tries to read from localhost resolver. Restart the service solves the problem, but I have to restart the service everytime I reboot.Steps to reproduce
Log files
Configuration file
Environment information