A NAS is not overkill considering at a bare minimum it's simply file storage made available over the network. Technically speaking, another 1tb SSD connected to a pi and shared over the network as file storage would be considered network attached storage. Anyhow, if you plan on moving data away from the cloud I'd highly suggest mirroring two disks in case something happens to one of them. If your simply using it for a local backup then a single SSD I'd say is fine.
j0nathanr
joined 1 year ago
If you already have adgaurd set up with your custom A records, all you have to do is point your client's dns to the IP of your adgaurd instance. If your running this on your router, than put your router's IP address as your client's dns. Use nslookup to troubleshoot dns requests and local domain lookup. If you have an A record "test.mydomain", run "nslookup test.mydomain" and reply with the results if the lookup doesn't work. Additionally if you'd like test to resolve to test.mydomain, you would have to include the search domain "mydomain" in your dns configuration.
Find out what port(s) is used by ABS to serve the audiobooks (if your not sure look at their documentation).Assuming it's https (port 443), log into your router and port forward 443 from the IP of your ABS instance. Test the connection from a device off your network by using your public IP address as the server name (you may have to specify the port you forwarded depending on the client software. e.g: yourpublicip:443).
Once you confirm the connection works, now you have to test it using your domain name. Why? Because you won't be able to access your ABS instance while on your local network using your public IP, you have to use the local one. This is where domain names and dns comes into play and makes things a whole lot more complicated (but that's the fun of it :D).
Accessing your ABS instance externally using your domain name is easy, all you have to do is create an A record for example "ABS" and point it to your public IP address. So now abs.yourdomain.com will resolve to your public IP address (sounds like you already have done this with DDNS just make sure to create your desired A record). Using abs.yourdomain.com as the server name for you ABS instance should now work off your local network.
Internally, you need a DNS server to resolve abs.yourdomain.com to it's local IP address (a simple DNSmasq server would work fine). Then you need to point your client devices to use your internal dns server for dns requests (this can be done manually from the device or from your router's dhcp server). Now requests to abs.yourdomain.com will resolve to ABS' local IP address while on your local network so both internal and external access should work seamlessly.