validation of . failed: resource limit exceeded.

[Nic0w]

Versions

Core version is v6.0.5 (Latest: N/A)
Web version is v6.0.2 (Latest: N/A)
FTL version is v6.0.4 (Latest: N/A)

Platform

• OS and version: Raspbian

• Platform: Kubernetes

Expected behavior

I expect DNSSEC to be working.

Actual behavior / bug

DNSSEC does not work.

Steps to reproduce

Steps to reproduce the behavior:

Deploy pihole.

Additional context

Pihole is hosted on a IPv6 single stack kubernetes cluster, as such I'm unable to upload any logs to tricorder.pi-hole.net

Upstream server is an unbound server (dual stack)

Startup logs

pihole-688bd4d7d7-6m5vm_logs.txt

Unbound config

unbound.txt

[yubiuser]

It seems, you got general connectivity issues

fatal: unable to access 'https://github.com/pi-hole/pi-hole/': Failed to connect to github.com port 443 after 7 ms: Could not connect to server
fatal: unable to access 'https://github.com/pi-hole/web/': Failed to connect to github.com port 443 after 1 ms: Could not connect to server
fatal: unable to access 'https://github.com/pi-hole/FTL/': Failed to connect to github.com port 443 after 1 ms: Could not connect to server

[Nic0w]

Hi @yubiuser,

It is github.com, not me, which is having general connectivity issues, by not supporting IPv6. See https://github.com/orgs/community/discussions/151477

As said in my post, my kubernetes cluster is IPv6 only.

Do you think not being able to reach pi-hole repositories causes my issue with DNSSEC ?

[yubiuser]

Oh, i didn't thought GitHub is IPv4 only in 2025...

Do you think not being able to reach pi-hole repositories causes my issue with DNSSEC ?

No. Also the DNS root servers should be reachable via IPv6.
I think it would be helpful to get the corresponding unbound log, but you did not specify a log file.

---

One year ago we had a bug hiding behind this warning indnsmasq so I move this to the FTL repo

[DL6ER]

It's much more likely that you'll get a good answer if you contact the dnsmasq team directly at [email protected]. They can also work on a fix we'll swiftly incorporate into Pi-hole once they have one. They are aware of Pi-hole FTL and that it embeds a (minimally) modified version of dnsmasq and that's no issue for them.