The reason that I have not set this up is due to the fact that there are many topics/forum posts/articles/blogs out there that have different opinions of what should be entered into the text box. I believe I read somewhere that this isn’t something that is required for a locally server DNS Server, but I am interested in hearing opinions (and what exactly that it does).Ĭorrect me if I am wrong, but shouldn’t this be enabled since I am using Unbound, which is a DNSSEC Resolver?Īs of writing this post, I only see my LAN Clients’ IP Address rather than their Hostname - however, I do not mind NOT seeing their Hostname. Enable Reverse Resolving of Clients’ IP Addresses (Second Image).Use Private Reverse DNS Resolvers (Second Image).Enable EDNS Client Subnet (First Image).
Thank God I was able to recover the data.).I am currently running AdGuard Home and Unbound on a Raspberry Pi 4B and was wondering about a few DNS settings within the AdGuard Home web GUI.
I corrupted my DB and had to use the innodb flag to get it back online (which was a byzantine nightmare searching through Local’s cryptic labeling system in Application Support to directly add the flag. It may resolve your problem!Īnd please do NOT just quit the Local app. Try turning off wifi or any Ad block software (local or DNS level including pihole and things like that). Anyways, thought it might be useful to someone on the forum who may struggle with esoteric spinning beach balls of death. I switched to Cloudflare’s DNS and was able to keep my AdGuard app as is. Not sure why this specific combo causes this problem. If I turn off wifi or turn off AdGuard, or change the AdGuard DNS on the router, it fixes the problem. When both of these conditions are met, and I turn on the Local app, the app will freeze, without fail. I finally narrowed down the user case to having both AdGuard turned on (the mac app) and having AdGuard DNS + Family Filter added at the router level. I have been struggling for the past few weeks to resolve a hang up with the Local app on my Mac.
0 kommentar(er)
