no DNS Resolver Infrastructure Cache Stats with forwarding

4o4rh

I have forwarding enabled, but DNS Resolver Infrastructure Cache Stats are zero for everything.

If i run below, i get no results

unbound-control -c /var/unbound/unbound.conf dump_cache | grep nine.com.au

If i then run nslookup from a client and re-run the above command, i get

unbound-control -c /var/unbound/unbound.conf dump_cache | grep nine.com.au
nine.com.au.    897     IN      SOA     ns-1268.awsdns-30.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
nine.com.au.    57      IN      A       3.105.141.15
nine.com.au.    57      IN      A       13.236.89.249
msg nine.com.au. IN AAAA 33152 1 897 0 0 1 0
nine.com.au. IN SOA 4
msg nine.com.au. IN A 33152 1 57 0 1 0 0
nine.com.au. IN A 0

so caching is definitely working, but why don't i get any statistics?

bingo600

@gwaitsi

Would be decent to provide : pfSense version and pfSense platform

/Bingo

4o4rh

@bingo600 was the same on 2.4.5_p1 and now 2.5.0. J1900 headless

bingo600

@gwaitsi
Could it be that it is strictly forwarding ?

I'm also using pfSense DNS forwarding (only , no 127.0.0.1 lookups) , but have never bothered to check statistics.
Are statistics the pict below ??

I have lots of cache entries.

/root: unbound-control -c /var/unbound/unbound.conf dump_cache | wc
    2528   16972  167440

/Bingo

4o4rh

@bingo600 yes, that is what i mean. all the "DNS Resolver Infrasture Cache Stats" are 0. but as the command shows, it is caching.

bingo600

@gwaitsi

It really depends ...

You have told it to forward , that could mean no cache lookups are allowed.
It might still cache the lookups, when received. Just not allowed to use them.

/Bingo