envoyproxy / envoyproxy/envoy

no_default_search_domain does not take effect

Open
#33,138 6 comments 2 reactions 0 assignees View on GitHub
area/dns bug help wanted
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 22h
Merged PRs (30d)
430

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](https://github.com/envoyproxy/envoy/assets/32058494/cf885baa-728c-4c2b-aed0-cbfa544c247b)

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

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.