DnsServer completely destroyed by one change

[plethora9]

I don't think there is any recovery for this since it is hosted on AWS and it can no longer connect. The DnsServer was working fine and when I made the changes below, it became bricked.
I added block lists for domains that are less than a month old. I saved and then flushed DNS cache on the web admin portal and clicked Save again.
I then clicked on App Store.
Everything just crashed.
Web portal stops responding.
DNS queries no longer being resolved, cannot ping Google.
I can still ping the instance.
I tried rebooting the instance in AWS, unresponsive. I did a shutdown in AWS. Instance stopped.
I powered the instance back on. I assigned it an elastic IP so the public IP doesn't change.
Web portal still not functional. SSH no longer worked either so I can't remote in. I can still ping it but DNS queries still don't work.
So basically, I activated a nuke by that order of operations above. I don't see a way to recover since I am completely locked out without SSH. Also the other connection methods in AWS EC2 don't work either.
So I have no choice but to rebuild.
This is on the latest version that I updated to 2 days ago. 14.2 or something.
Sharing just in case someone wants to try and recreate in a test build to see if it is reproducible. This was on a Debian 13 x86-64 build. AMI: debian-13-amd64-20251006-2257

[ShreyasZare]

Thanks for the post. The NRD lists are large and contain millions of entries. The 28 day list will load around 10mn domain names to block and take around 1.8 GB memory. You will need to increase the RAM on your AWS instance to something like 4GB to be able to use these NRD lists. You should be able to recover this AWS instance by increasing its RAM and rebooting.

[plethora9]

Thanks for the reply. I failed to realize the RAM requirements of said lists. I had to raise the instance to 8 GB to get it responsive enough to remove the NRD lists. Rebooted and now it is back down to 600 MB. I'll definitely pay more attention to that. Thanks again.

[ShreyasZare]

Good to know the issue is resolved now. Also note that when the block lists update, it will load the downloaded lists in memory before replacing the existing lists. So the DNS server will be briefly using almost double memory and will take a while for clearing the memory used by older lists.