Those kind of errors have received elevated visibility with recent Pi-hole releases, although they'd always been properly logged on occurence before (likely without anyone noticing them).
See the discussion from DNSMASQ_WARN reducing DNS packet size - #9 by DL6ER, which lead to us updating our documentation on dnsmasq warnings, specifically:
reducing DNS packet size for nameserver
ADDRESStoSAFE_PKTSZWhen receiving answers from upstream only with a smaller maximum DNS packet size,
dnsmasqwarns about this and remembers this decision per server for some time (defaulting to 60 seconds).If you see this message continuously, you are affected by some unusual truncation on the path from your Pi-hole to the configured upstream server. You can get rid of the warning by adding a config file like
/etc/dnsmasq.d/99-edns.confand addingedns-packet-max=1232After running
pihole restartdnsyour Pi-hole will not even try larger packet sizes (the default is 4096). Check out our unbound guide for a comment about the particular value of1232.