favonia

@nmbrg Thanks for the question! And thanks for using this tool. :grinning: I feel the proper solution is to add another entry in the FAQ section of README, and maybe...

@nmbrg I see. Is it correct to say that the updating itself is not working, so you checked the logging, and then found the probing errors? If so, you can...

I still want to see the error messages to check that it's not a bug about the code itself, if possible. Thanks!

@nmbrg Hmm I now think maybe 1.1.1.1 is working but the imposed time limit (1 second) is too short. On the other hand I'm concerned about a longer time limit....

@nmbrg I opened a new issue #858 based on my current understanding. Please let me know if it matches your experience. I feel there might be other issues not covered...

@nmbrg Thank you. The "cron" thing can indeed be very misleading. Usually it's a cron service running a "cron job" to update DNS records, but that's not the case here....

@nmbrg I guess the only way to figure out is to measure the actual time you need to complete the probing. If you can run `curl` on the same machine,...

No I don't need to see the HTTP headers output by `curl`. The following command will show the total connection time: ```bash curl --output /dev/null --silent --write-out 'Total time: %{time_total}s\n'...

@nmbrg Thank you. The time record of 0.06 seconds is certainly fast enough to finish any probing. I don't understand the root issue (that is, somehow the Go equivalent takes...

@nmbrg I didn't actually follow my original plan. Instead, I just implemented a variant of the Happy Eyeballs (Fast Fallback) algorithm to work around the 1.1.1.1 blockage. You should not...