Package: dnsmasq
Version: 2.61-1
Severity: normal

With dnsmasq, I am supposed to just see 127.0.0.1 in my
/etc/resolv.conf. The actual nameserver entries, based on my network
connection state, should be updated in /var/run/dnsmasq/resolv.conf.
This is the expectation when using dnsmasq + resolvconf.

My config is customized as per the recommendations. But still,
resolvconf keeps committing changes into /etc/resolv.conf, which,
forfeits the whole idea of install dnsmasq.


At the time of this writing, with the attached dnsmasq settings in this
bug report, the following is the state of /etc/resolv.conf

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by
# resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.2.1
nameserver 10.73.158.106
nameserver 10.73.158.107


In its current state, how is dnsmasq supposed to be used? Or is it a
buggy behavior I am facing?

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages dnsmasq depends on:
ii  adduser       3.113+nmu2
ii  dnsmasq-base  2.61-1
ii  netbase       5.0

dnsmasq recommends no packages.

Versions of packages dnsmasq suggests:
ii  resolvconf  1.65

-- Configuration Files:
/etc/default/dnsmasq changed:
ENABLED=1
CONFIG_DIR=/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new
IGNORE_RESOLVCONF=yes

/etc/dnsmasq.conf changed:
resolv-file=/var/run/dnsmasq/resolv.conf


-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to