DNSmasq stops working randomly

My setup requires DNSmasq, as my router does not support nat loopback. Previously it has worked well, but now it appears to no longer work (will randomly go out - worked fine this morning, now it doesn’t). I’m not getting any error messages on the add-on page or within HA’s logs. I believe since it is unresponsive, my devices now also ignore it as the preferred DNS server.

Results from nslookup using my HA instance with DNSmasq turned on. I believe this should return my local IP address, correct?

nslookup my-ha-domain.duckdns.org 192.168.xx.xxx
;; connection timed out; no servers could be reached

I can access HA fine via IP, but no longer via domain. The app doesn’t like this however, and will no longer connect from my home network. Any ideas why this is being problematic, or where to start debugging?

Can someone running DNSmasq and DuckDNS do me a favor? I want to make sure this SHOULD work as I think it should, but isn’t. Run nslookup your-ha-domain.duckdns.org xxx.xxx.xx.xx , where xxx.xxx.xx.xx is the IP address of your HA instance, and the duckdns is your domain. I get a ;; connection timed out; no servers could be reached, but if it was working properly I believe you should see your internal HA IP get resolved as the server address. Trying to debug my setup here and see why its not working now, but always has in the past. Thanks in advance.