DNS

Chute uses a customized DNS client to support advanced features. It may behave differently from the DNS client of your operating system.

Chute will play as DNS server when session applied DIRECT rule. Chute will check the DNS record of host first, then initial the socket with IP returned in the DNS record. With this method, all session applied DIRECT rule will bypass system DNS configuration and route with Chute DNS server.

Chute iOS will config system DNS server to Chute DNS server.

Upstream DNS Server

Chute uses the DNS server addresses from the operating system by default. You can override them with DNS server, DoH (DNS-over-HTTPS), DoT (DNS-over-TLS), DoQ (DNS-over-QUIC), and DoH3 (DNS-over-HTTP/3) services using 'dns-server' option.

DNS Section

DNS options are normally written in [General], but they may equivalently be written under a top-level [DNS] section: dns-server, doh (aliases doh-server, doh-service), dot, doq, doh3, direct-dns-server, proxy-dns-server, encrypted-dns-server, allow-dns-svcb, encrypted-dns-follow-outbound-mode, hijack-dns and always-real-ip behave the same in either section. The very same section also accepts local DNS mapping lines, the per-domain form used in [Host], so both line forms may coexist in one section. Any other key is first read as a mapping line: a key = value with no IP address and no server:-style prefix becomes an alias, so a [General] key misplaced here — optimistic-dns = false — silently maps the name optimistic-dns to false instead of raising an error. Only a line the mapping parser rejects as well is ignored with a notice in the log. fallback-dns-server and encrypted-dns-skip-cert-verification are read here too.

[DNS]
doh = https://dns.google/dns-query
always-real-ip = *.lan
*.example.com = server:1.1.1.1

Details

Chute simultaneously queries all DNS servers to improve performance, similar to dnsmasq with '--all-servers' parameter. The first answer from servers will be used. Chute iOS app and Chute Dashboard will show which server responds first. If Chute has not received any answer in 2 seconds, it will query all servers again. Note that only DNS server, DoT and DoQ upstreams participate in retries; DoH, DoH3 and syslib are queried on the first round only. After 3 retries (4 attempts in total) or 10 seconds, Chute will give up and report DNS error. On Chute iOS, Chute Mac and Chute tvOS a pool that holds an encrypted server is not asked again on that 2-second timer: it is asked once — the encrypted servers, then the plain ones when none of them answers, see How the Servers Are Asked — and only the 10-second limit applies. These retries cover Chute's own lookups and the questions it takes over from the TUN interface and the SOCKS5 UDP relay; a question sent straight to Chute's DNS listening port goes to the servers once and is not retried, so its client's own retry takes over.

Which servers are asked depends on the name. A domain whose rule verdict is DIRECT uses direct-dns-server when it is set, the host names of proxy servers use proxy-dns-server, a domain with a local DNS mapping uses the server assigned there, and everything else uses the main pool (dns-server, doh, dot, doq, doh3). direct-dns-server serves the lookups Chute makes when it dials a direct connection, and an app's question only when the question reaches Chute's resolver: under TUN, apps' A and AAAA questions are answered with fake IPs instead. When a dedicated pool returns no answer, the query is retried on the main pool; when the main pool returns no answer, fallback-dns-server is asked once before the error is reported.

Some domain names may have poorly-performing authoritative name servers, causing upstream DNS servers to return empty answer due to server-side timeout or other connectivity issues. Chute will report empty DNS error to upstream DNS servers explicitly return empty DNS answers, or if some servers return empty answers and the others have not responded 0.3 seconds later.

On every platform — Chute Mac without Enhanced Mode and Chute Android in Local Proxy mode included — Chute also judges whether the IPv6 way out is actually working. While it judges it dead — IPv6 is on, but dials to public IPv6 destinations go unanswered — it may, for a while, answer AAAA questions for a name that has an A record with an empty answer, put IPv4 addresses first, and dial a DIRECT connection to an IPv6 address whose name is known on that name's A record. It probes again in the background and resumes IPv6 by itself; there is no setting for this, and a working IPv6 way out is not affected.

Some DNS record has very short TTL due to configuration, Chute enforces a minimum TTL of 60 seconds: shorter TTLs are raised to 60 seconds. Optimistic DNS is enabled by default — the cached DNS result is returned immediately while refreshing in the background. It can be disabled via optimistic-dns = false. An NXDOMAIN answer that carries the zone's SOA record is cached as well, for the time that record gives for negative answers — the smaller of its own TTL and its MINIMUM field, at most one day, and not at all when that is zero; until it expires, the name is answered NXDOMAIN without asking the servers again. An upstream NXDOMAIN answer is not cached when a matching [Host] mapping or alias takes precedence.

The DNS cache keeps 200 records. On iOS, tvOS and Android it is never allowed to grow without bound: a request for an unlimited cache is refused, the 200-record cache is kept, and a notice says so.

When IPv6 is available and enabled, Chute DNS client will send both A and AAAA questions to upstream DNS Servers. The first A or AAAA answer returned will be used. On single-stack networks, an answer for an address family that is currently not routable is held back in favor of the other family, and is only used as a fallback when the other family yields nothing.

S. Smart Rabbit LLC © All Rights Reserved            updated 2026-11-18 12:01:58

results matching ""

    No results matching ""