Wildcard SSL not working

[ali-master]

Describe the bug
I configured the server, and when it wants to generate wildcard SSL, it returns this error:

caddy-1     | {"level":"error","ts":1723990466.3546808,"logger":"tls.obtain","msg":"could not get certificate from issuer","identifier":"*.mydomain.com","issuer":"acme-v02.api.letsencrypt.org-directory","error":"[*.mydomain.com] solving challenges: waiting for solver certmagic.solverWrapper to be ready: checking DNS propagation of \"_acme-challenge.go.revue.ir\": read udp 127.0.0.1:49927->127.0.0.1:53: read: connection refused (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/159763563/18490867073) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)"}

It tries to connect to the localhost instead of the Server's public IP:

read udp 127.0.0.1:49927->127.0.0.1:53

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[amalshaji]

Can you provide more information? Are you running this locally?

[ali-master]

Yes, I'm running it on a Server with a public IP

[amalshaji]

Are ports 80 and 443 open?

[ali-master]

Are ports 80 and 443 open?

Yes.

1. What other potential reasons for the attempt to resolve from the 127.0.0.1 IP instead of the Public Server IP?
2. Have you considered the possibility of network configuration issues causing the attempt to resolve from the 127.0.0.1 IP?
3. How would you address someone who argues that the attempt to resolve from the 127.0.0.1 IP does not necessarily indicate that ports 80 and 443 are open?

[amalshaji]

What domain are you using?