On 9/24/2016 06:05, Erich Titl wrote: > Am 24.09.2016 um 09:06 schrieb Andrew: >> On 24.09.2016 04:22, Erich Titl wrote: >>> I never understood why the standard resolver >>> file was not used, but this is all personal preference. If dhcpcd would >>> write to /etc/resolv.conf and dnsmasq would read from it (as it does on >>> my installation) then all this would is moot, because /etc/resolv.conf >>> is saved as it is the standard. >> Maybe because host system also uses dnsmasq as caching DNS relay - so it >> require '127.0.0.1' in /etc/resolv.conf > > I _believe_ it should be possible to force such behaviour by placing > 127.0.0.1 into resolv.conf.head. > >From Simon Kelleys' website and man page of dnsmasq (quote): http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html -r, --resolv-file=<file> Read the IP addresses of the upstream nameservers from <file>, instead of /etc/resolv.conf. For the format of this file see resolv.conf(5). The only lines relevant to dnsmasq are nameserver ones. Dnsmasq can be told to poll more than one resolv.conf file, the first file name specified overrides the default, subsequent ones add to the list. This is only allowed when polling; the file with the currently latest modification time is the one used. -R, --no-resolv Don't read /etc/resolv.conf. Get upstream servers only from the command line or the dnsmasq configuration file.
More info how to use/setup /etc/resolv.conf: http://oss.segetech.com/intra/srv/dnsmasq.conf ------------------------------------------------------------------------------ ------------------------------------------------------------------------ leaf-user mailing list: leaf-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
