Your message dated Mon, 07 Oct 2024 20:42:45 +0200
with message-id <[email protected]>
and subject line Re: dnsmasq breaks dns lookup with resolvconf
has caused the Debian Bug report #777004,
regarding dnsmasq breaks dns lookup with resolvconf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
777004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777004
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dnsmasq
Version: 2.72-2
Severity: important
Hello,
Apparently
1) dnsmasq registers itself as nameserver 127.0.0.1 for interface lo
with resolvconf.
2) resolvconf registers lo as highest priority and stops processing
after encountering 127.0.0.1 nameserver
3) dnsmasq reads nameservers to forward to from /etc/resolv.conf which
is generated by resolvconf which only puts the dnsmasq entry in the file
Ergo there is no name resolving done once dnsmasq is started.
Please fix the dnsmasq scritpts to not break name resolution on machine
running dnsmasq.
Thanks
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable'), (171, 'unstable'), (151,
'experimental'), (121, 'precise-updates'), (121, 'precise-security'), (121,
'precise'), (101, 'stable'), (101, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.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
Init: systemd (via /run/systemd/system)
Versions of packages dnsmasq depends on:
ii dnsmasq-base 2.72-2
ii init-system-helpers 1.22
ii netbase 5.3
dnsmasq recommends no packages.
Versions of packages dnsmasq suggests:
ii resolvconf 1.76.1
-- Configuration Files:
/etc/dbus-1/system.d/dnsmasq.conf 9a18c8a761c2262dbf0c8b3345a85242 [Errno 2] No
such file or directory: u'/etc/dbus-1/system.d/dnsmasq.conf
9a18c8a761c2262dbf0c8b3345a85242'
/etc/default/dnsmasq changed:
ENABLED=1
CONFIG_DIR=/etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new
IGNORE_RESOLVCONF=no
/etc/dnsmasq.conf changed:
dhcp-range=10.0.0.33,10.0.0.255,255.255.255.0,12h
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Michal,
On Wed, 04 Feb 2015 00:41:07 +0100 Michal Suchanek <[email protected]> wrote:
> Package: dnsmasq
> Version: 2.72-2
> Severity: important
>
> Hello,
>
> Apparently
>
> 1) dnsmasq registers itself as nameserver 127.0.0.1 for interface lo
> with resolvconf.
>
> 2) resolvconf registers lo as highest priority and stops processing
> after encountering 127.0.0.1 nameserver
>
> 3) dnsmasq reads nameservers to forward to from /etc/resolv.conf which
> is generated by resolvconf which only puts the dnsmasq entry in the file
>
> Ergo there is no name resolving done once dnsmasq is started.
>
> Please fix the dnsmasq scritpts to not break name resolution on machine
> running dnsmasq.
>
The issue you reported does not seem to exist anymore, it may have been
fixed implicitely in the past. Closing this bug therefore.
Cheers,
Sven
--
GPG Fingerprint
3DF5 E8AA 43FC 9FDF D086 F195 ADF5 0EDA F8AD D585
signature.asc
Description: This is a digitally signed message part
--- End Message ---
