-
|
We're using the Talos HostDNS feature (https://docs.siderolabs.com/talos/v1.12/networking/host-dns). I was wondering about timeouts for requests to upstream DNS servers if there is a cache miss. I found this in the code: https://github.com/siderolabs/talos/blob/main/internal/pkg/dns/dns.go#L54 Is my assumption correct, that this is the timeout that is being applied to upstream DNS requests? Are there any plans to make this configurable in the host DNS feature (Happy to help out with a PR if you think that is worth to do...). Thank you! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
You are correct in your assessment, the timeout is set to 4.5 seconds. The reason is that default resolver timeout in applications is usually 5 seconds, so if Host DNS processes the response for longer than that, an incorrect error would pop up at the application level: as if the Host DNS timed out, while it's actually the upstream DNS server which timed out. What would be the reason to change this value? |
Beta Was this translation helpful? Give feedback.
You are correct in your assessment, the timeout is set to 4.5 seconds. The reason is that default resolver timeout in applications is usually 5 seconds, so if Host DNS processes the response for longer than that, an incorrect error would pop up at the application level: as if the Host DNS timed out, while it's actually the upstream DNS server which timed out.
What would be the reason to change this value?