Please follow the below template, it will help us to help you!
If you are Experiencing issues with a Pi-hole install that has non-standard elements (e.g you are using nginx, apache2 or another reverse proxy, or there is some other aspect of your install that is customised) - please use the Community Help category.
Expected Behaviour:
I have registered a wildcard subdomain with my registry. The resolution works fine outside of my home. Behind PiHole all clients cannot resolve any subdomain matching the wildcard.
Operating System (Family and Version): raspbian 13
Hardware raspberry pi 4B
Docker compose file or Docker run command: docker compose
Docker engine version 29.9.0
I would expect that the IP address is resolved correctly.
I defined custom dns entries in PiHole for my important subdomains. I would like to not be needing this.
Actual Behaviour:
Resolution is tested on Android, Macos, iOS and always returns cannot resolve host.
Debug Token:
Replace this text with the debug token provided from running pihole -d
My guess is that dns.domain.name is set to your registered domain. With dns.domain.local = true (the default), Pi-hole then answers every name in that domain itself and never asks upstream, so only the names you added as custom DNS records resolve. If that's the case, either set dns.domain.name back to a purely local name, e.g., lan, or set dns.domain.local = false so the other names are forwarded upstream again.
Then my guess was wrong, dns.domain is not the cause and you should leave it as it is. With dns.domain.local = false, unanswered queries for *.pi.hole would go to your upstream servers, which helps nothing here.
Please run, with one of the wildcard names that fails:
and post both outputs, with your domain in place of example.com. Also tell me whether the wildcard points to a private address such as 192.168.x.x: several routers and upstream resolvers drop such answers as DNS rebinding.