Lines Matching full:upstream
61 Negative replies from upstream servers normally contain time-to-live
63 replies from upstream servers omit this information, dnsmasq does not
214 with "no such domain" rather than being forwarded upstream.
217 Modify IPv4 addresses returned from upstream nameservers; old-ip is
244 Read the IP addresses of the upstream nameservers from <file>, instead of
254 Don't read /etc/resolv.conf. Get upstream servers only from the command
259 configuration which can be changed is upstream DNS servers (and
264 By default, dnsmasq will send queries to any of the upstream servers
270 By default, when dnsmasq has more than one upstream server available,
276 Reject (and log) addresses from upstream nameservers which are in the
290 or domain parts, to upstream nameservers. If the name is not known
294 Specify IP address of upstream servers directly. Setting this flag does
317 but should never forward queries on that domain to any upstream
348 answered from /etc/hosts or DHCP and not sent to an upstream
421 "no such domain" answers from upstream nameservers and answer
1052 of names that have been inserted into the cache. For each upstream
1082 forwards such queries to a fully recursive upstream DNS server which is
1086 addresses of the upstream nameservers it should use, since the
1114 Upstream servers may also be specified on the command line or in
1122 dnsmasq. Then either specify the upstream servers directly to dnsmasq
1133 names in the upstream DNS, so "mycompany.com 1.2.3.4" in /etc/hosts will ensure that
1135 the upstream DNS would otherwise return a different address. There is
1136 one exception to this: if the upstream DNS contains a CNAME which
1223 performance depends too on the performance of the upstream
