I'm setting up a k3s cluster on a bunch of Raspberry pi cards on my home network. I have an odd issue, and I'm looking for a work around. My external-facing internet DNS resolves to a different IP than my internal one does, because my external address isn't route-able from my internal network (weird home network router, I guess.) I've got all my nodes set up using internal DNS, but when a challenge is created, the self-check is always finding the external one, and thus fails:
Reason: Waiting for http-01 challenge propagation: failed to perform self check GET request 'http://tyrellcorp.tplinkdns.com/.well-known/acme-challenge/2rYNmqNC15ox0Qc77Ul6siv3-DK_yHMTItMmjHYEfcs': Get http://tyrellcorp.tplinkdns.com/.well-known/acme-challenge/2rYNmqNC15ox0Qc77Ul6siv3-DK_yHMTItMmjHYEfcs: dial tcp 73.67.246.179:80: connect: connection timed out
The challenge is in fact presented externally (if I hit that URL from outside my network, I see it.) So I need to do one of two things:
- Configure the self-check to use my internal DNS rather than whatever it's using, or
- Disable the self-check and let the challenge proceed.