Eugene
Eugene
@ameshkov, we actually have a piece of logic that restricts caching custom upstream results: https://github.com/AdguardTeam/dnsproxy/blob/0f484364e76f7d9a435a5d06ba2ef2393f30f118/proxy/proxy.go#L481 This is the result of fixing AdguardTeam/AdGuardHome#1301. Should we leave it as is or implement...
@marriva, hello. The Dnsmasq's documentation states: > Matching of domains is normally done on complete labels, so /google.com/ matches google.com and www.google.com but NOT supergoogle.com. This can be overridden with...
@yscialom, hello and apologies for late response. We've pushed the modified version of this PR to the [separate branch](https://github.com/AdguardTeam/AdGuardHome/tree/4728-cap-check). Could you please try to build AdGuard Home from the latest...
@abdalians, hello again and apologies for late response. It actually seems AdGuard Home still serves local DNS zones, resolving the requests with appropriate local data, at least I can see...
@ve6rah, that is weird if the local network is ok. Are you able to reproduce it? If yes, could you please also capture a verbose log for us? This would...
@abdalians, @sammyke007, @fuomag9, @james-1987, could you please capture the [verbose log](https://github.com/AdguardTeam/AdGuardHome/wiki/FAQ#verboselog) for us? Unfortunately, we still can't reproduce it. It would also be helpful to look at the exact moment...
Hi @nmreadelf, sorry for the late reply and thanks for the contribution. As far as I know, [RFC-4361 Section 6.1](https://www.rfc-editor.org/rfc/rfc4361#section-6.1), which updates the referenced [RFC-2132](https://www.rfc-editor.org/rfc/rfc2132.html#section-9.14), actually forbids using the hardware...
Could it be related to #6438? It seems the `v0.108.0-b.50` has indeed got some memory management issues which should be fixed in `edge` releases. Could you please try one of...
@wangqaq, which actual part of the returned HTTP response corresponds to this upstream? It may be related to the test we perform for healthchecking the servers, so this one may...
@jkreileder, hello and apologies for the late response. We've pushed the `edge` build, that fixes the behavior of TLD domain specifications. I suppose something like the following will work well...