Lines Matching full:will
11 This is not a security hole since dnsmasq will only accept replies to that
17 specified, the operating system will select an available port number
48 Q: Will dnsmasq compile/run on non-Linux systems?
52 in /contrib. Dnsmasq will link with uclibc to provide small
81 so the above will not work when the bogus-priv option is set.
110 using "nslookup" or "dig" will work, but then attempting to run
111 "ping" will get a lookup failure, appending a dot to the end of the
112 hostname will fix things. (ie "ping myhost" fails, but "ping
116 Any domain will do, but "localnet" is traditional. Now when you
117 resolve "myhost" the resolver will attempt to look up
140 go off-line and then on-line again will not lose the contents of
164 --bogus-nxdomain flag. Dnsmasq will check for results returning
228 default client-id will be 01:<MAC address>, so change the dhcp-host
260 socket will receive _all_ packets sent to port 53, no matter what
265 socket bound to 0.0.0.0 its source address will be set to the
279 wildcard binding means that dnsmasq will quite happily start up
331 will recognise the same machine, and use the same address. The
342 that this will work fine only as longer as only one interface is
345 this rule, bad things will happen.
374 nameserver configured dnsmasq will load-balance across them and
424 A: Yes, as a DNS server, dnsmasq will just work in a vserver.
426 extra system capabilities. Please note that doing so will lesser
443 there's a potential problem with deadlock: the syslog daemon will
445 these lookups will (depending on exact configuration) go through
448 dnsmasq is waiting for syslog; they will both wait forever. This
454 then those queries will in turn generate two more log lines, and a
455 chain reaction runaway will occur. To avoid this, use syslog-ng
