[pihole] [unbound] [DNSMASQ] validation failed: resource limit exeeded

DL6ER · February 19, 2024, 1:02pm

The fix issued by dnsmasq is now available via

pihole checkout ftl release/v5.25.1

github.com/pi-hole/FTL

Fix spurious "resource limit exceeded" messages (v5 backport)

pi-hole:master ← pi-hole:release/v5.25.1

opened 01:06PM - 19 Feb 24 UTC

DL6ER

+4 -4

# What does this implement/fix? Backports https://github.com/pi-hole/FTL/pull…/1892 to FTL v5.25 - aiming straight for a bugfix release. --- **Related issue or feature (if applicable):** https://discourse.pi-hole.net/t/pihole-unbound-dnsmasq-validation-failed-resource-limit-exeeded/68388 **Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) ## Checklist: - [x] The code change is tested and works locally. - [x] I based my code and PRs against the repositories `developmental` branch. - [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions - [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship - [x] I have read the above and my PR is ready for review.

for the Pi-hole FTL v5.25 users, and

pihole checkout ftl fix/dnsmasq_resource_warning

github.com/pi-hole/FTL

Fix spurious "resource limit exceeded" messages

pi-hole:development-v6 ← pi-hole:fix/dnsmasq_resource_warning

opened 01:05PM - 19 Feb 24 UTC

DL6ER

+4 -4

# What does this implement/fix? This PR imports https://thekelleys.org.uk/git…web/?p=dnsmasq.git;a=commitdiff;h=1ed783b8d7343c42910a61f12a8fc6237eb80417: > Replies from upstream with a REFUSED rcode can result in log messages stating that a resource limit has been exceeded, which is not the case. and updates the version of the embedded `dnsmasq` server. --- **Related issue or feature (if applicable):** https://discourse.pi-hole.net/t/pihole-unbound-dnsmasq-validation-failed-resource-limit-exeeded/68388 **Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A --- **By submitting this pull request, I confirm the following:** 1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against. 2. I have commented my proposed changes within the code. 3. I am willing to help maintain this change if there are issues with it later. 4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1) 5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)) ## Checklist: - [x] The code change is tested and works locally. - [x] I based my code and PRs against the repositories `developmental` branch. - [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions - [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship - [x] I have read the above and my PR is ready for review.

for the v6.0 beta users.

Please test and verify the warning does not show up again.

edit You should also remove the custom file we created during testing using

sudo rm /etc/dnsmasq.d/99-dnssec-limits.conf
sudo service pihole-FTL restart