Open up2you1 opened 1 week ago
Hello
You can check the entries in console, using redis-cli command. Then, inside the redis cli, you use the command KEYS * It will show you all the entries it has stored. It increases each time it stores a new one. In a fresh start you can easily see it increasing as you execute dns request in // to test
(I'm on my phone, I can't copy paste any screenshot, I hope you get it)
No if your redis container is restarted, every entries will be lost because, by default, Redis stores data in RAM. To retain data, you can use snapshotting (RDB) or Append-Only File (AOF). But I never tried.
Yes it's a great combo, my upstream is ~2ms response time, now. š
Hello
You can check the entries in console, using redis-cli command. Then, inside the redis cli, you use the command KEYS * It will show you all the entries it has stored. It increases each time it stores a new one. In a fresh start you can easily see it increasing as you execute dns request in // to test
(I'm on my phone, I can't copy paste any screenshot, I hope you get it)
No if your redis container is restarted, every entries will be lost because, by default, Redis stores data in RAM. To retain data, you can use snapshotting (RDB) or Append-Only File (AOF). But I never tried.
Yes it's a great combo, my upstream is ~2ms response time, now. š
Thank you, yes can see it increasing :)
im at 10ms, after only one evening, should get better over the next few days.
Hello, are you using it in recursive mode or with public DNS ?
I have deleted the "forward-queries.conf" file to use it as a recursive DNS but compared to you, I have a poor response time, 40ms after 2 days. My classical adguard docker without unbound have a 4ms response time.
Have I missed something ? Or should I use public DNS for better performance ? Thanks.
Hello, are you using it in recursive mode or with public DNS ?
I have deleted the "forward-queries.conf" file to use it as a recursive DNS but compared to you, I have a poor response time, 40ms after 2 days. My classical adguard docker without unbound have a 4ms response time.
Have I missed something ? Or should I use public DNS for better performance ? Thanks.
Iām using it with public dns, yesterday was quad9, today Iām trying ControlD
I use forwarding-queries. To Cloudflare dns which have the best answer time for me.
I use forwarding-queries. To Cloudflare dns which have the best answer time for me.
do you think the malware lists in Adguard is enough rather than using say Quad9 which as builtin malware?
Chances are that adguard's will be better and more frequently updated. Lists are a big part of their business, and they publish and maintain many of them. And of all bottles, more specifically, I don't like quad9. In the past they've had several breakdowns. Now, breakdowns happen to all companies, including adguard dns, but quad9 boasted 99.99% availability, even though we weren't there at all. After a few comments on twitter and some time passing, they removed their text from their site.
Chances are that adguard's will be better and more frequently updated. Lists are a big part of their business, and they publish and maintain many of them. And of all bottles, more specifically, I don't like quad9. In the past they've had several breakdowns. Now, breakdowns happen to all companies, including adguard dns, but quad9 boasted 99.99% availability, even though we weren't there at all. After a few comments on twitter and some time passing, they removed their text from their site.
thanks! ive given ControlD a try.
Firstly great work with this, i used to use this one before: https://github.com/ar51an/unbound-redis but so much involved getting it to work, this docker in unraid is literraly plug and play, so hats off to you!
My question, because ADH optimistic cache isnt swtched on as its using unbound/redis, is there anyway to see if caching is working?
also i assume being redis, persistent caching is enabled so even when the docker is rebooted it would still keep cached entries yes?
Thanks!