Anubhav

In the node local DNS logs, 63 unique DNS resolutions occurred before Envoy declared readiness. However, envoy’s DNS logs revealed 73 queries (both successful and failed) before the same readiness...

More details: 1. Looked into DNS constraints in AWS EC2 instances. And the limit has not been breached 2. Tested with 3k service entries using STRICT_DNS, and that reduced the...

@yuval-k @howardjohn - is this the correct way to enable DNS over TCP? ```yaml apiVersion: networking.istio.io/v1alpha3 kind: EnvoyFilter metadata: name: dns-over-tcp namespace: test spec: workloadSelector: labels: app: test configPatches: -...

Tried this: ```yaml apiVersion: networking.istio.io/v1alpha3 kind: EnvoyFilter metadata: name: dns-over-tcp namespace: test spec: workloadSelector: labels: app: test configPatches: - applyTo: CLUSTER patch: operation: MERGE value: #use_tcp_for_dns_lookups: true dns_resolution_config: #typed_config: #"@type":...

This should be redundant now. @shriramsharma please confirm.

@Ben131-Go : can you please validate with the current master?

Few questions: 1. What are the different environments in question? 2. When does the merge issue occur?

@ku9nov: the readme has been updated, can you please try now? @tibers: can you please retry now. We recently pushed a lot of pending changes to upstream. Please let me...

@resnostyle: can you please validate this with the current master? We pushed a lot of changes recently.

We see a lot of timeouts, is there a way to configure timeouts? I see there is an option in the c-ares library ARES_OPT_TIMEOUT, but don't see an option to...