hank you for the reply. In fact, the older version of Boulder is working perfectly fine for me.
I’m just trying out the latest version, but I’m not sure if there’s anything else I need to do to point Boulder to a DNS server IP — in other words, is there any configuration required beyond setting FAKE_DNS?
In the older version, the default port for HTTP-01 was not port 80, so I had to change it manually. But as I understand, the latest version uses port 80 by default.
I’m confident it will work fine — I just wanted to confirm:
Is it expected that while resolving the domain, Boulder uses the IP assigned by FAKE_DNS to resolve the IP of the host running Certbot? as you can see my error log the ip is my dns server not the certbot host ip it supposed to be host ip right ? or am i wrong ?
i also can see a dns parameter in docker as below do i have to add my dns server ip here ?
# Use consul as a backup to Docker's embedded DNS server. If there's a name
# Docker's DNS server doesn't know about, it will forward the query to this
# IP (running consul).
# (https://docs.docker.com/config/containers/container-networking/#dns-services).
# This is used to look up service names via A records (like ra.service.consul) that
# are configured via the ServerAddress field of cmd.GRPCClientConfig.
# TODO: Remove this when ServerAddress is deprecated in favor of SRV records
# and DNSAuthority.
dns: 10.55.55.10
thanks in advance.