I have some ip rules in dae rules, but dae will also request dns once when accessing these ip, is this a bug caused by domain name sniffing, or is this a feature?
My dns uses the local adguardhome, and these requests occur when connecting to telegram
The following is my configuration file, I removed some privacy content
global {
lan_interface: eth0
wan_interface: eth0
tcp_check_url: 'http://cp.cloudflare.com'
tcp_check_http_method: HEAD
udp_check_dns: 'dns.google:53'
log_level: info
allow_insecure: false
auto_config_kernel_parameter: true
}
node {
'ss node use aes-256-gcm'
}
# 更多的 DNS 样例见 https://github.com/daeuniverse/dae/blob/main/docs/en/configuration/dns.md
dns {
upstream {
localdns: 'udp://192.168.5.53:53'
}
routing {
request {
fallback: localdns
}
}
}
group {
proxy {
#filter: name(keyword: HK, keyword: SG)
policy: min_moving_avg
}
}
# 更多的 Routing 样例见 https://github.com/daeuniverse/dae/blob/main/docs/en/configuration/routing.md
routing {
# main
pname(NetworkManager) -> must_direct
sip(192.168.5.53) && l4proto(udp) && dport(53) -> must_direct
dip(224.0.0.0/3, 'ff00::/8') -> direct
dip(geoip:private) -> direct
dip(geoip:cn) -> direct
domain(geosite:gfw) -> proxy
domain(geosite:netflix) -> proxy
domain(suffix: cm.steampowered.com) -> direct
domain(suffix: steamserver.net) -> direct
domain(geosite:steam@cn) -> direct
domain(geosite:steam) -> proxy
domain(geosite:microsoft@cn) -> direct
domain(geosite:microsoft) -> proxy
dip(geoip:telegram) -> proxy
# fallback
fallback: direct
}
Checks
Support Request
I have some ip rules in dae rules, but dae will also request dns once when accessing these ip, is this a bug caused by domain name sniffing, or is this a feature?
Current Behavior
Expected Behavior
I think these connections should not request dns
Steps to Reproduce
My dns uses the local adguardhome, and these requests occur when connecting to telegram The following is my configuration file, I removed some privacy content
Environment
Anything else?
No response