istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update ttl for proxy dns resolution (#15967) 

* update ttl for proxy dns resolution

* Update content/en/docs/ops/configuration/traffic-management/dns/index.md

Co-authored-by: Craig Box <craig.box@gmail.com>

* re-phrase ttl for dns resolution

---------

Co-authored-by: Craig Box <craig.box@gmail.com>
This commit is contained in:
Navin ILango 2024-11-21 03:15:42 -06:00 committed by GitHub
parent 927cfea88d
commit e8c8e211bf
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/ops/configuration/traffic-management/dns/index.md
View File

@ -58,7 +58,7 @@ a static list of IPs or by doing its own DNS resolution (potentially of the same
Unlike most clients, which will do DNS requests on demand at the time of requests (and then typically cache the results), Unlike most clients, which will do DNS requests on demand at the time of requests (and then typically cache the results),
the Istio proxy never does synchronous DNS requests. the Istio proxy never does synchronous DNS requests.
When a `resolution: DNS` type `ServiceEntry` is configured, the proxy will periodically resolve the configured hostnames and use those for all requests. When a `resolution: DNS` type `ServiceEntry` is configured, the proxy will periodically resolve the configured hostnames and use those for all requests.
This interval is determined by the [TTL](https://en.wikipedia.org/wiki/Time_to_live#DNS_records) of the DNS response. This interval is fixed at 30 seconds and cannot be changed at this time.
This happens even if the proxy never sends any requests to these applications. This happens even if the proxy never sends any requests to these applications.
For meshes with many proxies or many `resolution: DNS` type `ServiceEntries`, especially when low `TTL`s are used, this may cause a high load on DNS servers. For meshes with many proxies or many `resolution: DNS` type `ServiceEntries`, especially when low `TTL`s are used, this may cause a high load on DNS servers.