DNSMASQ Warnings

I believe since a recent update the dnsmasq warnings are displayed more clear and that the warnings were always present but not shown in the GUI?

I keep getting these warning below sometimes up to 70 a day is this normal or should I change something?

reducing DNS packet size for nameserver 1.1.1.1 to 1232
reducing DNS packet size for nameserver 1.0.0.1 to 1232
reducing DNS packet size for nameserver 2606:4700:4700::1111 to 1232
reducing DNS packet size for nameserver 2606:4700:4700::1001 to 1232

The Pi-hole diagnosis warnings link to a page with explanations for each dnsmasq warning type, which also would list ways to address them, if applicable.

Did you try those suggestions yet?

Ah Thanks

I believe a few months ago I checked and this information wasn't there.
I seem to get the errors around every hour

Are there any tests I can do to see where this bottleneck is happening?
My setup is BT Router > Switch > Pihole/PC

It is one of your upstream DNS servers that is imposing that limit.

That would be Cloudflare

Is there a way of seeing what DNS requests are causing these warnings? Maybe its a particular device causing it to happen

The particular DNS request isn't of an interest here - it will happen any time an upstream rejects a packet as too large. That is a normal occurrence, and the DNS protocol covers for this by having a client repeat the request via TCP.

If you'd follow the linked suggestion, you wouldn't see this warning anymore, as Pi-hole would then always use TCP immediately for packets exceeding your upstream's reported UDP limit.

Right cheers for the help I will get the setting changed.

The only reason I was confused that it may be a particular device was it only shows around every 2 hours and according to DL6ER Cloudflare Max packet size should be 1452 not 1232

The Cloudflare DNS servers shown in your log output are imposing a limit of 1232. If you want to avoid future warnings, set that as your dnsmasq limit.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.