This is probably the way, because a traditional “mail server” is actually 4-5 different servers working together.
And they can all be very easily misconfigured to break everything completely. Great learning experience though.
Nextcloud has collabora integrated.
I would put this stuff behind VPN.
Seems weird to me, the router would need to do deep packet inspection of DNS and selectively block specific ones. It feels more like you’ve set up your DNS to do forwarding instead of resolution. Can you post a network diagram and the DNS config?
Do tcpdump host $server instead. Otherwise you will only see the request (the response goes to a different port).
Just to be sure you do dig A @server $domain (with the “A”) and can confirm the following
SERVER is your server
;; ANSWER SECTION is empty (or doesn’t exist)
;; AUTHORITY SECTION mentions your local DNS server
Also check
dig NS @server $domain
Is your server in the answer section?
Here is how I would diagnose (I’m assuming you have Linux / WSL on a client)
dig $domain check which server answereddig a $domain should give a recorddig a $domain @server to make sure you’re querying the right serverIf none work, probably network issue (DNS boind to wrong IP, firewall, etc)
If 3 and 5 work but 4 doesn’t, your DNS isn’t authorative.
If only 5 works DNS settings on the client is wrong.
I would put truenas on the NAS, also put a VM on truenas with 16-24G of RAM.
Create a kubernetes or docker swarm cluster with server 1 and the nas vm and just have everything as containers. This way you just have one resource pool, and the containers will be started wherever there are enough resources available. The containers will mount NFS shares from truenas which truenas will create automatically as ZFS datasets. ZFS supports snapshots.