| 2012-08-27 14:50:15 |
Pete Graner |
bug |
|
|
added bug |
| 2012-08-27 14:51:53 |
Mathieu Trudel-Lapierre |
dnsmasq (Ubuntu): status |
New |
Confirmed |
|
| 2012-08-27 14:51:57 |
Mathieu Trudel-Lapierre |
dnsmasq (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-08-27 14:52:04 |
Mathieu Trudel-Lapierre |
dnsmasq (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2012-08-28 12:09:47 |
Thomas Hood |
affects |
dnsmasq (Ubuntu) |
network-manager (Ubuntu) |
|
| 2012-08-28 12:11:04 |
Thomas Hood |
summary |
dnsmasq updating resolvconf when it's not configured to do DNS |
network-manager dnsmasq configuration snippet causes standalone dnsmasq not to listen on 127.0.0.1, breaking name service when dnsmasq is installed |
|
| 2012-08-28 15:15:17 |
Thomas Hood |
bug |
|
|
added subscriber Thomas Hood |
| 2012-08-29 18:15:54 |
Mathieu Trudel-Lapierre |
affects |
network-manager (Ubuntu) |
dnsmasq (Ubuntu) |
|
| 2012-08-29 18:15:54 |
Mathieu Trudel-Lapierre |
dnsmasq (Ubuntu): status |
Confirmed |
Triaged |
|
| 2012-08-31 13:45:45 |
Thomas Hood |
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 |
|
| 2012-09-13 06:56:46 |
Timo Aaltonen |
bug |
|
|
added subscriber Timo Aaltonen |
| 2012-09-14 21:06:24 |
Mathieu Trudel-Lapierre |
dnsmasq (Ubuntu): assignee |
Mathieu Trudel-Lapierre (mathieu-tl) |
|
|
| 2012-12-11 09:38:53 |
Gab |
bug |
|
|
added subscriber Gab |
| 2013-01-28 10:08:02 |
Thomas Hood |
description |
The system dnsmasq is preventing nameservice from working with NetworkManager. By setting /etc/deafault/dnsmasq ENABLED=1 to ENABLED=0, nameservice started working again.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: dnsmasq (not installed)
ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2
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..etc.default.dnsmasq: 2012-08-27T10:43:43.717591
mtime.conffile..etc.dnsmasq.conf: 2012-05-26T23:51:39.391123 |
The standalone Dnsmasq (from the dnsmasq package) is preventing the NetworkManager-controlled dnsmasq from starting. By setting ENABLED=0 in /etc/default/dnsmasq instead of ENABLED=1, name service started working again.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: dnsmasq (not installed)
ProcVersionSignature: Ubuntu 3.5.0-12.12-generic 3.5.2
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..etc.default.dnsmasq: 2012-08-27T10:43:43.717591
mtime.conffile..etc.dnsmasq.conf: 2012-05-26T23:51:39.391123 |
|
| 2013-07-08 11:09:41 |
Thomas Hood |
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) |
|
| 2016-09-19 02:22:31 |
pdf |
bug |
|
|
added subscriber pdf |
