Re: [Dnsmasq-discuss] Implications of raising dns-forward-max

2023-07-03 Thread Petr Menšík
I think these kinds of problem arises usually when connectivity to upstream is broken or interrupted. 150 is number of concurrent queries waiting for resolution. It should not be required to increase this limit if the remote server is answering fast. Unless I am mistaken, as soon as the respon

Re: [Dnsmasq-discuss] Implications of raising dns-forward-max

2023-06-29 Thread Eric Fahlgren
On Thu, Jun 29, 2023 at 12:52 AM Buck Horn wrote: > Blindly increasing dns-forward-max without having analysed the actual > issue does not seem to recommend itself as the best option available to > me, even if it would turn out that actual resource impacts are minor. > > Stopping or unconfiguring

Re: [Dnsmasq-discuss] Implications of raising dns-forward-max

2023-06-29 Thread Buck Horn
Hi Eric, On 28.06.2023 03:35:38, "Eric Fahlgren" wrote: A couple posts on the OpenWrt forum have indicated that they are having DNS issues that are resolved by raising the forward limit from OpenWrt's default of 150 to 500. dns-forward-max=500 Assuming that there are indeed a lot of queries

[Dnsmasq-discuss] Implications of raising dns-forward-max

2023-06-27 Thread Eric Fahlgren
A couple posts on the OpenWrt forum have indicated that they are having DNS issues that are resolved by raising the forward limit from OpenWrt's default of 150 to 500. dns-forward-max=500 Assuming that there are indeed a lot of queries going on simultaneously, what does this affect? Does it incr