Lines Matching full:upstream
33 directly to the upstream server(s) instead.
39 (3) Time-to-live data from upstream server is read and
43 (5) Dnsmasq can get its upstream servers from
70 (ie dnsmasq is told to use itself as an upstream server.)
77 (6) Generate queries to upstream nameservers with unpredictable
85 never forward them to an upstream server. If the name is not in
117 upstream servers we send queries to. This fixes a problem
145 from an upstream nameserver, it will cache that information
195 talk to upstream servers via IPv6 if it finds IP6 addresses
228 Clear "truncated" bit in replies we return from upstream. This
340 upstream servers in the order they appear in /etc/resolv.conf.
342 Added upstream server use logging.
347 Added -S option to directly specify upstream servers and
366 upstream servers to forward a query to, return REFUSED.
451 to talk to upstream servers. Useful for people who want
541 upstream nameservers. This is useful with multihomed
1024 upstream load.
1034 Log replies from upstream servers which refuse to do
1036 relies on upstream servers to do the recursion, this
1198 with an IPv4 address in /etc/hosts which fails upstream
1200 is still tried upstream, but a NXDOMAIN reply gets
1341 the upstream value of the CNAME's target into the cache,
1388 Only warn once about an upstream server which is refusing to do
1459 with different upstream nameservers, as the host moves
2130 set and an upstream server returns a SERVFAIL
2217 Correctly garbage-collect connections when upstream
2399 to contact an upstream DNS server can be nailed
