Closed Folliant closed 8 months ago
Hello, this is correct behavior. When Unbound has cache contents for a name (but not an ANY query yet), for an ANY query it will try to get "some" records from the cache. If there is nothing cached, it will forward the ANY query upstream and then it depends on how the upstream replies.
In your "non-working" case when you first populate the cache with only the A record, the subsequent ANY query will immediately find that in the cache and return it.
Also in your working example, after 60 seconds (the lowest TTL on answer), that answer will be expired and an ANY query will return just a subset of those records you see there from the cache.
Hello. I've faced a situation, when after the command
dig google.com A
Unbound doesn't return value fordig google.com ANY
. Thank you for your time.Environment:
Docker container:
Unbound version:
Unbound config:
Path:
Content:
Issue:
Expected behaviour: