Don’t mix your public and private DNS records. Use your public records for public things, and a local DNS forwarder for your local network.
A records only reference IPs and not ports.
SRV can be used to specify where to find ports, but the client needs to support those lookups to properly use it. You can use a reverse proxy or HTTP redirects to point things to different ports.
If it fails it’s healthcheck, then it reports unhealthy. Check and see what it’s healthcheck is configure to be.
Doesn’t look like anything integrates with it yet except for something called Mastopod.
Can’t tell if this is for real.
I really think you have conflicting resolvers running on startup, which would explain this. Double check your systemd units that are enabled on boot. If you don’t see anything like networkmanager, reboot the machine, get the status of systemd-resolv to make sure it’s actually running after a fresh boot, check the logs and see if you see anything interesting there, then restart it and check the logs again once DNS works. Something is different between those two actions.
See if this helps at all:
sudo systemctl revert systemd-resolved
sudo systemctl restart systemd-resolved
Also, what does ls -lh /etc/resolv* show?
What’s happening in journalctl -u systemd-resolved?
Well only your DNS is broken, so that’s all that needs to get fixed. Are you POSITIVE you’re using systemd resolve and not networkmanager?
Did you insert the sysctl values and reboot?
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Synology sells single bay units now, but anything that has network connectivity should work fine. If this is just off-site backup, find whatever is the cheapest. If an RPi with a USB attached disk is cheaper, do that.
You can find MiniPCs of all sorts really cheap now, though almost all have smaller onboard SSD storage.
Removed by mod
They aren’t comparable being at completely different scales. Check https://diskprices.com/