Ok is this a dnsmasq issue? I whitelisted 1.8.168.192.in-addr.arpa in dnscrypt, which appears as blocked when AMTM searches for updates. I still get upd err, suggesting this could be a server side issue. Dnsmasq is sneaking these PTR requests through for some odd reason, maybe because of sever connection errors without PTR? And it does not enforce blocks 100% with dnsmasq.conf.
I still see
You said it is blocked at the router level, where could this be blocked in my router as you suggested
@thelonelycoder? I can ping diversion.ch via the terminal, and curl pulls your website without any issue.
I see no block in dnscrypt, dnsmasq, or skynet. Reinstalled AMTM, no change.
Also
@thelonelycoder I do not see dns requests in diversion/dnsmasq logs when running AMTM update, why not, what resolver is it using? and where can I find those logs for debugging?