Ainar Garipov

We cannot reproduce this. These statistics could simply be caused by these clients requesting a larger quantity of diverse domains. A better way to see if the request has been...

@schzhn, please look into this. @WildByDesign, just to be clear, is the upstream just another popular DNS service or a custom server? Perhaps the upstream is making the results uncacheable?

@WildByDesign, just in case, OpenDNS is one of the servers with known cacheability issues. See AdguardTeam/KnowledgeBaseDNS#16.

I'm not sure what this feature request is really about, sorry. The statistics currently do show the period, e.g.: > for the last 90 days Can you rewrite the request...

@thewonderer73, I see. There is only one statistics period, so the graphs can be assumed to have the same period as the tables below. @Sakura-Luna, I'm not sure what you're...

@Sakura-Luna, I see, you mean the fix we've committed recently. I'll retitle this issue to be about a unit toggle then.

As far as I know there is an internal address for containers, usually within 172.17.0.0/16 subnet. See . Have you tried resolving `adguardhome.` from within the containers?

Hello and thank you for the thorough report. Does `nslookup 'www.example.com' '::1'` work? The main theory here is that the system doesn't process dual-stack sockets the way the Go runtime...

Yes, seems like FreeBSD doesn't send IPv4 queries to an IPv6 sockets by default, which is why your configuration with both IPv4 and IPv6 localhost addresses works. So it is...

I don't have that error. Can you show the resulting YAML? ```yaml dns: bind_hosts: - '0.0.0.0' - '::' ```