Please enhance dnsmasq to talk directly to resolvconf and to register only its actual listening address(es)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dnsmasq (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
The standalone Dnsmasq (from the dnsmasq package) is preventing the NetworkManager-
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: dnsmasq (not installed)
ProcVersionSign
Uname: Linux 3.5.0-12-generic x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Date: Mon Aug 27 10:48:06 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile.
mtime.conffile.
summary: |
- network-manager dnsmasq configuration snippet causes standalone dnsmasq - not to listen on 127.0.0.1, breaking name service when dnsmasq is - installed + dnsmasq should not register 127.0.0.1 with resolvconf if it's not + listening on lo |
description: | updated |
summary: |
- dnsmasq should not register 127.0.0.1 with resolvconf if it's not - listening on lo + Please enhance dnsmasq to talk directly to resolvconf and to register + only its actual listening address(es) |
The issue seems to be that with its current configuration (and including "bind-interfaces", and "except- interface= lo"), dnsmasq tries to update DNS via resolvconf which adds a file under /run/resolvconf /interface/ lo.dnsmasq.
That file contains 'nameserver 127.0.0.1', which is absolutely incorrect given the configuration, at least because of except-interface.
This nameserver configuration in resolvconf appears to take precedence over the NetworkManager provided configuration (nameserver 127.0.1.1) also running dnsmasq.