It doesn't like how you have something configured. The error message provides indication of such. It is pointing to your private upstream section. Not the main part where you have placed your Google, cloudflare, and quad9 at.
www.snbforums.com
spot on advice this was complete user error not sure why i had these entries there: i removed them and all is well now i believe these entries were there by defaultIt doesn't like how you have something configured. The error message provides indication of such. It is pointing to your private upstream section. Not the main part where you have placed your Google, cloudflare, and quad9 at.
Please check out posts around this thread.
AdGuardHome - Asuswrt-Merlin-AdGuardHome-Installer (AMAGHI) cont.
Sorry I think I am not being clear. I am not talking about local logging of queries. I am talking about at the DNS provider level. Here is another way to look at it, if the only cloudflare server near your geolocation goes down; and, you are using that cloudflare server you may notice a service...
Basically, You have a non-local arpa listed in the Private Upstream section. Only arpas for private ranges can be specified there, (e.g. 1.1.168.192.arpa).
AdGuardHome has determined that you have an arpa for a non-private address range listed in this section. In order to use a non-private address arpa, you must specify it in the same upstream section where you listed these lines:
The top two would be fine, the one that was causing the issue is the last one.
9.204.in-addr.arpa is not apart of a private range.thank you so much i added the top two lines back
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!