envoyproxy/envoy

no_default_search_domain does not take effect

Open

#33,138 opened on Mar 27, 2024

View on GitHub
 (6 comments) (2 reactions) (0 assignees)C++ (5,373 forks)batch import
area/dnsbughelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

no_default_search_domain in dns_resolver_options does not take effect

Description: I am using dynamic_forward_proxy cluster, and sub_clusters_config is selected. To suppress too many request towards local DNS, I configured DNS resolver in cluster level image

But the test result is that envoy still search the default domain, and dns resolution failed in my case. my host name in request is: a.com my expectation is envoy query a.com directly to my configured dns server the result is envoy query a.com.mynamespace.svc.cluster.local, mynamespace.svc.cluster.local is the first records in my /etc/resolv.conf

in my /etc/resolv.conf: search mynamespace.svc.cluster.local svc.cluster.local cluster.local abcd nameserver 1.1.1.1 options ndots:5

Contributor guide