podman Pi-hole and wildcard domains not working

[Greylinux]

@Bucking_Horn

If you want your Pi-hole to handle ALL types for a domain internally, you'd have to add the equivalent of local=/.mydomain.dedyn.io/ for your specific domain to your custom configuration.

Of course, if you'd do that and you'd have to rely on certain types returning specific answers, you'd have to also add the respective definitions for those types (e.g. CNAME would return NODATA then, where public DNS may have answered with mydomain.dedyn.io).

I'm not sure I entirely understand all of this, but adding local after address seems to work

address=/.mydomain.dedyn.io/192.168.1.250 
local=/.mydomain.dedyn.io/ 

every nslookup shows

core@fedora-coreos:~$ nslookup mydomain.dedyn.io
Server:         192.168.1.250
Address:        192.168.1.250#53

Name:   mydomain.dedyn.io
Address: 192.168.1.250

@Bucking_Horn

If you want your Pi-hole to handle ALL types for a domain internally,

does this mean that when I request a new cert or renewal it will also resolve to 192.168.1.250? if so can I add _acme-challenge.mydomain.dedyn.io to resolve to _acme-challenge.mydomain.dedyn.io like in the adguard config above?

@Bucking_Horn

I don't see a reason why your installation behaves differently, unless perhaps you'd have some extra configuration details not shared yet.

could this be the configuration I have setup with my domain provider?

as a quick overview , I have one A record pointing to my home IP ( although it will never be used as its entirely local) and 4 CNAME records ( probably why it makes requests to CNAME directly) pointing to the target domain that's the one listed in the A record

@Bucking_Horn

Nevertheless, you should probably be aware that you are shadowing public DNS records

is this because I am using a second level subdomain for my domain name, provided by https://desec.io ?

I'm more than happy to send a screenshot of my domain provider config if its possible privately?