Skip to content

Commit 1c99b54

Browse files
committed
docs: update docs to explains what happens when DNS request fails
1 parent 2c20e50 commit 1c99b54

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

docs/sources/gateway.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -113,8 +113,12 @@ The targets of the DNS entries created from a \*Route are sourced from the follo
113113
adding each address's `value`.
114114

115115
If the `--resolve-gateway-load-balancer-hostname` flag is specified, any address with type
116-
`Hostname` is queried through DNS and any resulting IP addresses are added instead of the hostname.
117-
A DNS query failure results in zero targets being added for that address.
116+
`Hostname` is queried through DNS and any resulting IP addresses are added instead of the hostname,
117+
producing `A`/`AAAA` records rather than a `CNAME`.
118+
119+
If DNS resolution fails for a hostname address (e.g. the hostname is unresolvable or the DNS
120+
server is unavailable), the error is logged the `Endpoint` of that address is skipped entirely. If all of a Gateway's addresses fail to resolve, the route will produce no
121+
endpoints for that reconciliation cycle and will be retried on the next sync.
118122

119123
The targets from each parent Gateway matching the \*Route are then combined and de-duplicated.
120124

0 commit comments

Comments
 (0)