# 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.
# No DNS servers known.
search .
For whatever reason you have installed systemd-resolved. This is not needed at all. Maybe something that OMV comes with? If possible, you should uninstall it as you are using STATIC IP.
I don’t know 
Just installed diepi, nginx and openmediavault.
For what is it?
I’m using DCHP, dietpi gets the ip from my router
/edit
maybe systemd-resolved is from docker I installed with openmediavault?
systemd-resolved is a systemd service that provides network name resolution to local applications via a D-Bus interface.
At least from our side, it is not installed and not required.
The screenshot above says something different. It said SATIC and not DHCP.
Quoting myself
just apt remove systemd-resolved and DNS name resolution might be working?
Check content of /etc/resolv.conf after removing the package. It should continue the DNS server provided by your DHCP server
cat: /etc/resolv.conf: No such file or directory
hm no name resolution 
Switch to static ip once, and back to DHCP. Does it generate the file?
No.
- Command: curl -ILfvm 10 https://dietpi.com/
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
[ OK ] DietPi-Config | sed --follow-symlinks -i / iw dev .* set power_save /d /etc/network/interfaces
[ SUB1 ] DietPi-Set_hardware > wifimodules (disable)
[ OK ] DietPi-Set_hardware | Desired setting in /boot/config.txt was already set: dtoverlay=disable-wifi
[ OK ] DietPi-Set_hardware | eval echo 'blacklist brcmutil' >> /etc/modprobe.d/dietpi-disable_wifi.conf
[ OK ] DietPi-Set_hardware | modprobe -rf brcmutil
[ OK ] DietPi-Set_hardware | eval echo 'blacklist brcmfmac' >> /etc/modprobe.d/dietpi-disable_wifi.conf
[ OK ] DietPi-Set_hardware | modprobe -rf brcmfmac
[ OK ] DietPi-Set_hardware | eval echo 'blacklist cfg80211' >> /etc/modprobe.d/dietpi-disable_wifi.conf
[ OK ] DietPi-Set_hardware | modprobe -rf cfg80211
[ OK ] wifimodules disable | Completed
[ INFO ] DietPi-Config | Restarting network connections, please wait...
[ OK ] DietPi-Config | systemctl daemon-reload
[ INFO ] DietPi-Config | systemctl restart ifup@eth0, please wait...
Apr 18 15:07:17 DietPi systemd[1]: Stopping ifup@eth0.service - ifup for eth0...
Apr 18 15:07:17 DietPi dhclient[2803]: Removed stale PID file
Apr 18 15:07:17 DietPi ifdown[2803]: Removed stale PID file
Apr 18 15:07:17 DietPi ifdown[2803]: Internet Systems Consortium DHCP Client 4.4.3-P1
Apr 18 15:07:17 DietPi ifdown[2803]: Copyright 2004-2022 Internet Systems Consortium.
Apr 18 15:07:17 DietPi ifdown[2803]: All rights reserved.
Apr 18 15:07:17 DietPi ifdown[2803]: For info, please visit https://www.isc.org/software/dhcp/
Apr 18 15:07:17 DietPi dhclient[2803]: Internet Systems Consortium DHCP Client 4.4.3-P1
Apr 18 15:07:17 DietPi dhclient[2803]: Copyright 2004-2022 Internet Systems Consortium.
Apr 18 15:07:17 DietPi dhclient[2803]: All rights reserved.
Apr 18 15:07:17 DietPi dhclient[2803]: For info, please visit https://www.isc.org/software/dhcp/
Apr 18 15:07:17 DietPi dhclient[2803]:
Apr 18 15:07:17 DietPi dhclient[2803]: Listening on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifdown[2803]: Listening on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifdown[2803]: Sending on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifdown[2803]: Sending on Socket/fallback
Apr 18 15:07:17 DietPi dhclient[2803]: Sending on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi dhclient[2803]: Sending on Socket/fallback
Apr 18 15:07:17 DietPi dhclient[2803]: DHCPRELEASE of 192.168.1.65 on eth0 to 192.168.1.1 port 67
Apr 18 15:07:17 DietPi ifdown[2803]: DHCPRELEASE of 192.168.1.65 on eth0 to 192.168.1.1 port 67
Apr 18 15:07:17 DietPi systemd[1]: ifup@eth0.service: Deactivated successfully.
Apr 18 15:07:17 DietPi systemd[1]: Stopped ifup@eth0.service - ifup for eth0.
Apr 18 15:07:17 DietPi systemd[1]: Starting ifup@eth0.service - ifup for eth0...
Apr 18 15:07:17 DietPi dhclient[2840]: Internet Systems Consortium DHCP Client 4.4.3-P1
Apr 18 15:07:17 DietPi ifup[2840]: Internet Systems Consortium DHCP Client 4.4.3-P1
Apr 18 15:07:17 DietPi ifup[2840]: Copyright 2004-2022 Internet Systems Consortium.
Apr 18 15:07:17 DietPi ifup[2840]: All rights reserved.
Apr 18 15:07:17 DietPi ifup[2840]: For info, please visit https://www.isc.org/software/dhcp/
Apr 18 15:07:17 DietPi dhclient[2840]: Copyright 2004-2022 Internet Systems Consortium.
Apr 18 15:07:17 DietPi dhclient[2840]: All rights reserved.
Apr 18 15:07:17 DietPi dhclient[2840]: For info, please visit https://www.isc.org/software/dhcp/
Apr 18 15:07:17 DietPi dhclient[2840]:
Apr 18 15:07:17 DietPi dhclient[2840]: Listening on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifup[2840]: Listening on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifup[2840]: Sending on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifup[2840]: Sending on Socket/fallback
Apr 18 15:07:17 DietPi dhclient[2840]: Sending on LPF/eth0/2c:cf:67:d4:3a:a0
Apr 18 15:07:17 DietPi ifup[2840]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Apr 18 15:07:17 DietPi dhclient[2840]: Sending on Socket/fallback
Apr 18 15:07:17 DietPi dhclient[2840]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Apr 18 15:07:20 DietPi dhclient[2840]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Apr 18 15:07:20 DietPi ifup[2840]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
[ OK ] DietPi-Config | systemctl restart ifup@eth0
[ INFO ] DietPi-Config | Reloading networking data, please wait...
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
[ OK ] DietPi-Config | Network restarted
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
[ ] DietPi-Config | Checking URL: https://dietpi.com/ (2/2) % Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Could not resolve host: dietpi.com
* Closing connection 0
curl: (6) Could not resolve host: dietpi.com
[FAILED] DietPi-Config | Checking URL: https://dietpi.com/
- Command: curl -ILfvm 10 https://dietpi.com/
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
mawk: cannot open /etc/resolv.conf (No such file or directory)
root@DietPi:~# cat /etc/resolv.conf
cat: /etc/resolv.conf: No such file or directory
Create it manually and try again
touch /etc/resolv.conf
touch: cannot touch '/etc/resolv.conf': No such file or directory
Do you use root user to do this?
Yes
Maybe resolv.conf is a symlink?
Try to remove it and touch again.
sudo rm -f /etc/resolv.conf
sudo touch /etc/resolv.conf
That worked! Thank you so much guys!
One more question, I just saw when I install openmediavault it will install systemd-resolved. Is there a way to bypass the DNS problem?