From: peasthope on 9 Aug 2010 11:30 Jaime, You put me back on track. Thanks! From: Jaime Di Cristina <jaime.dc(a)gmail.co.> Date: Sun, 08 Aug 2010 23:32:13 -0400 > I use dnsmasq on OpenWrt. There the information of the DNS > servers is stored on /tmp/resolv.conf.auto. I don't know where is the > equivalent location on a Debian installation of dnsmasq. Debian doesn't have /tmp/resolv.conf.auto but here is the answer. peter(a)joule:~$ ps aux | grep dnsmasq dnsmasq 5278 0.0 0.0 2328 592 ? S Aug08 0:00 /usr/sbin/dnsma sq -u dnsmasq -r /var/run/dnsmasq/resolv.conf peter 6774 0.0 0.0 3120 728 pts/0 S+ 07:56 0:00 grep dnsmasq >From the manual. -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, sub- sequent ones add to the list. This is only allowed when polling; the file with the currently latest modification time is the one used. And finally. peter(a)joule:~$ cat /var/run/dnsmasq/resolv.conf nameserver 64.59.160.[] nameserver 64.59.160.[] Last field omitted from the addresses in respect of the ISP. Strangely, the manual, FILES section, lists /etc/resolv.conf but not /var/run/dnsmasq/resolv.conf. I should have thought to check ps yesterday. All that is left in this story is to understand why dnsmasq uses /var/run/dnsmasq/resolv.conf rather than /etc/resolv.conf. Appears to be specific to Debian; not in other distributions. Is this a consequence of Debian policy? Thanks again, ... Peter E. -- Sparcstation 2, sun4c, netboots *.SUN4C; SCSI disks not yet detected. Personal site works; http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/171056585.34043.30778.(a)heaviside.invalid
|
Pages: 1 Prev: xulrunner stops upgrade Next: Re (2): finding the ip address for dns, nslookup & etc. |