You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pulled master as of today, and built with sudo go run main.go --config-path=config.yaml --verbose.
I run with the included configuration file, and then I simply hit the server with two dns questions over TLS. Both for google.com. Both requests make a dial out to an upstream provider, rather than using the cache, despite the cache being clearly enabled. Am I simply misunderstanding how caching works? That'd be embarrassing.
Run with Doggo: doggo google.com @tls://mydomain.example.com --time
Here is my verbose output:
Server start:
2024/09/06 11:45:52.910249 INFO dnsproxy starting version="" revision="" branch="" commit_time=""
2024/09/06 11:45:52.910496 DEBUG hosts files are enabled
2024/09/06 11:45:52.910508 DEBUG hosts files are not specified, using default paths=[private/etc/hosts]
2024/09/06 11:45:52.910830 DEBUG set upstream idx=0 addr=1.1.1.1:53
2024/09/06 11:45:52.910839 DEBUG set upstream idx=1 addr=8.8.8.8:53
2024/09/06 11:45:52.911905 INFO cache ttl override is enabled prefix=dnsproxy min=60 max=0
2024/09/06 11:45:52.911917 INFO ratelimit is enabled prefix=dnsproxy rps=20 ipv4_subnet_mask_len=24 ipv6_subnet_mask_len=56
2024/09/06 11:45:52.911941 INFO upstream mode is set prefix=dnsproxy mode=load_balance
2024/09/06 11:45:52.911946 INFO cache enabled prefix=dnsproxy size=64
2024/09/06 11:45:52.911951 INFO starting dns proxy server prefix=dnsproxy
2024/09/06 11:45:52.911989 INFO creating udp server socket prefix=dnsproxy addr=0.0.0.0:53
2024/09/06 11:45:52.912322 INFO listening to udp prefix=dnsproxy addr=[::]:53
My guess is that cache-size: 64 is not enough. That's 64 bytes, not entries. Try something bigger, e.g. 64000 or don't specify it, 64K is default. --cache-size= Cache size (in bytes). Default: 64k
Pulled master as of today, and built with
sudo go run main.go --config-path=config.yaml --verbose
.I run with the included configuration file, and then I simply hit the server with two dns questions over TLS. Both for google.com. Both requests make a dial out to an upstream provider, rather than using the cache, despite the cache being clearly enabled. Am I simply misunderstanding how caching works? That'd be embarrassing.
Here's some simple reproduction:
Run with Doggo:
doggo google.com @tls://mydomain.example.com --time
Here is my verbose output:
Server start:
Requests (two requests):
The text was updated successfully, but these errors were encountered: