module stuck at dns resolution

[qubusp]

The deployment i have is stuck at this for half an hour

module.aws-cluster.null_resource.wait_for_rancher[0]: Provisioning with 'local-exec'...
module.aws-cluster.null_resource.wait_for_rancher[0] (local-exec): Executing: ["/bin/sh" "-c" "while [ \"${subject}\" != \"*  subject: CN=${RANCHER_HOSTNAME}\" ]; do\n    subject=$(curl -vk -m 2 \"https://${RANCHER_HOSTNAME}/ping\" 2>&1 | grep \"subject:\")\n    echo \"Cert Subject Response: ${subject}\"\n    if [ \"${subject}\" != \"*  subject: CN=${RANCHER_HOSTNAME}\" ]; then\n      sleep 10\n    fi\ndone\nwhile [ \"${resp}\" != \"pong\" ]; do\n    resp=$(curl -sSk -m 2 \"https://${RANCHER_HOSTNAME}/ping\")\n    echo \"Rancher Response: ${resp}\"\n    if [ \"${resp}\" != \"pong\" ]; then\n      sleep 10\n    fi\ndone\n"]
module.aws-cluster.null_resource.wait_for_rancher[0] (local-exec): Cert Subject Response:
module.aws-cluster.null_resource.wait_for_rancher[0]: Still creating... [10s elapsed]
module.aws-cluster.null_resource.wait_for_rancher[0] (local-exec): Cert Subject Response:
module.aws-cluster.null_resource.wait_for_rancher[0]: Still creating... [20s elapsed]

[Ticiano-mw]

I have the same problem, I believe it's related to the LetsEncrypt failing to provision