"Waiting for DNS record propagation." and possible split DNS issue

[cirrusflyer]

@yeungalan, see thread here:

#49 (comment)

[tobychui]

@yeungalan any updates on this?

[cirrusflyer]

I was able to get a cert. But had to turn off some settings on my firewall related to DNS proxy and turn of my internal DNS. It would be nice if there was a way to tell Zoraxy what DNS server to use when looking for the domain. I believe LEGO allows this with the "--dns.resolvers" option and I'm using it with another piece of software.

[yeungalan]

will take a look, just came back from vacation

[lorddaren]

I am having the same issue. I see the records getting added to cloudflare but I can't get it to return within the docker container of zoraxy. I tried checking to see if I could somehow add something to the provider config but I am not sure how it would translate during the set up.

[mrg358]

I dealt with similar issue querying Cloudflare API and Letsencrypt certificates. Errors pointed to a DNS resolver issue. Hard setting cloudflare DNS into docker compose file resolved my problems. Zoraxy now pulls all certificates without any issue.

services:
  zoraxy-docker:
    image: zoraxydocker/zoraxy:latest
    container_name: zoraxy
    restart: unless-stopped
    dns:
      - 1.1.1.1
      - 1.0.0.1
    ports:
      - 80:80
      - 443:443
      - 8000:8000/tcp
    volumes:
      - config:/opt/zoraxy/config/
      - /var/run/docker.sock:/var/run/docker.sock
    environment:
      PORT: "8000"
      FASTGEOIP: "true"
      ARGS: '-noauth=false'

volumes:
  config:

[dschense]

Had the same Problem.
Running Adguard Home as my DNS server with Cloudflares Servers. Tested raw IP, DoH and DoT. No way to get the certs with Adguard as Middle.

Forced Zoraxy IP on my pfsense to bypass adguard and directly use cloudflare 1.1.1.1 when using port 53.
Its a simple NAT Port forward.

Source: Zoraxy IP
Dest. Port: 53
Dest. IP: 1.1.1.1

Now its working in seconds. Got any cert i requested.

[tobychui]

Seems this is an issue related to custom DNS in specific network environment. I am closing this as this is not an issue cause by Zoraxy.