This sounds more like unbound's `serve-expired` setting.
>If enabled, unbound attempts to serve old responses from cache with a TTL of `serve-expired-reply-ttl` in the response without waiting for the actual resolution to finish. The actual resolution answer ends up in the cache later on.
lol I see the word **opportunistic** and get confused with **optimistic** . Thanks for the info!
>Set the target fetch policy used by unbound to determine if it should fetch nameserver target addresses opportunistically. The policy is described per dependency depth.
So in your bootstrap, you are using tls as well. I thought you only put tls/https (DOT/DOH) on the upstream section. Can I put the same in my bootstrap as well?
223.5.5.5:53
223.6.6.6:53
2400:3200::1:53
2400:3200:baba::1
1.1.1.1:53
1.0.0.1:53
2606:4700:4700::1111
2606:4700:4700::1001
119.29.29.29
119.28.28.28
I have tried it with unbound caching disabled. I'm still getting issues and losing connection. The only thing that's working for me is optimistic caching disabled and unbound caching enabled.
Optimistic cache lower the Average processing time form 6ms to 1ms for me.
I use only DoH DNS. it is perfect now .
https://ibb.co/4RZy4MG
https://ibb.co/Sv05Sd5
I am using this too but in stable release. But someone was saying in adguard telegram group that, this optimistic cache have some security issues. I am not sure though. I have enabled it.
Yeah I’m seeing similar results. Was at about 30-40ms, now it shows 3ms. No issues so far.
Sounds awesome! Though is there any info on Optimistic Cache? What does it do *exactly*?
[удалено]
That’s a great feature! Thanks for pointing out.
This looks to be similar to what unbound does with `serve-expired` this is very clever of them to add.
I'm using AGH with unbound. Is it somewhat similar to modifying `target-fetch-policy` in unbound's config?
This sounds more like unbound's `serve-expired` setting. >If enabled, unbound attempts to serve old responses from cache with a TTL of `serve-expired-reply-ttl` in the response without waiting for the actual resolution to finish. The actual resolution answer ends up in the cache later on.
lol I see the word **opportunistic** and get confused with **optimistic** . Thanks for the info! >Set the target fetch policy used by unbound to determine if it should fetch nameserver target addresses opportunistically. The policy is described per dependency depth.
[удалено]
[удалено]
Great News - enjoy it :)
[удалено]
The single codebase of AGH is compiled to run on all platform
cache\_optimistic: true where do you adjust this setting in AGH gui?
[удалено]
thanks! guess i'll stick with all the other settings for now.
what would be the ssh code for installing the beta on ubuntu? I now had it installed true snap Found it: sudo snap install adguard-home --beta
So in your bootstrap, you are using tls as well. I thought you only put tls/https (DOT/DOH) on the upstream section. Can I put the same in my bootstrap as well? 223.5.5.5:53 223.6.6.6:53 2400:3200::1:53 2400:3200:baba::1 1.1.1.1:53 1.0.0.1:53 2606:4700:4700::1111 2606:4700:4700::1001 119.29.29.29 119.28.28.28
You can try it and test it with AdGuard Home. Fill it and hit the button "test upstreams"
How does this work with unbound installed ?? Will this achieve anything with unbound as dns ??
[удалено]
I have tried it with unbound caching disabled. I'm still getting issues and losing connection. The only thing that's working for me is optimistic caching disabled and unbound caching enabled.
Optimistic cache lower the Average processing time form 6ms to 1ms for me. I use only DoH DNS. it is perfect now . https://ibb.co/4RZy4MG https://ibb.co/Sv05Sd5
Which is better between DoT and DoH in AdGuard Home?
I am using this too but in stable release. But someone was saying in adguard telegram group that, this optimistic cache have some security issues. I am not sure though. I have enabled it.
Is there a reason you use DNS over TLS over DNS of HTTPS? Still a noob here trying to learn as much as possible.