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

Replace mention of virtual service with service entry in docs related to dns proxying (#13928)

This commit is contained in:
Radek Chrzanowski 2023-09-27 11:26:08 +02:00 committed by GitHub
parent 54c8aaaa9f
commit 5b97c97949
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
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

@ -35,7 +35,7 @@ Istio uses this information to determine the intended destination.
[Understanding Traffic Routing](/docs/ops/configuration/traffic-management/traffic-routing/) gives a deep dive into how this behavior works. [Understanding Traffic Routing](/docs/ops/configuration/traffic-management/traffic-routing/) gives a deep dive into how this behavior works.
If the client was unable to resolve the DNS request, the request would terminate before Istio receives it. If the client was unable to resolve the DNS request, the request would terminate before Istio receives it.
This means that if a request is sent to a hostname which is known to Istio (for example, by a `VirtualService`) but not to the DNS server, the request will fail. This means that if a request is sent to a hostname which is known to Istio (for example, by a `ServiceEntry`) but not to the DNS server, the request will fail.
Istio [DNS proxying](#dns-proxying) can change this behavior. Istio [DNS proxying](#dns-proxying) can change this behavior.
Once Istio has identified the intended destination, it must choose which address to send to. Once Istio has identified the intended destination, it must choose which address to send to.