Maybe I'm just confused about how resolvconf and dnsmasq should work,
but here's how it's working on my new 16.04 system:
root@ecoli:~# dpkg -l | grep dnsmasq
ii dnsmasq 2.75-1 all
Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-base 2.75-1 amd64
Small caching DNS proxy and DHCP/TFTP server
root@ecoli:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto enp0s10
iface enp0s10 inet static
address 160.36.130.174
netmask 255.255.255.0
network 160.36.130.0
broadcast 160.36.130.255
gateway 160.36.130.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 160.36.0.66 160.36.128.66 8.8.8.8
dns-search nimbios.org
root@ecoli:~# cat /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 127.0.0.1
search nimbios.org
root@ecoli:~# dpkg --purge dnsmasq
(Reading database ... 429253 files and directories currently installed.)
Removing dnsmasq (2.75-1) ...
Purging configuration files for dnsmasq (2.75-1) ...
root@ecoli:~# cat /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 160.36.0.66
nameserver 160.36.128.66
nameserver 8.8.8.8
search nimbios.org
root@ecoli:~# dpkg -l | grep dnsmasq
ii dnsmasq-base 2.75-1 amd64
Small caching DNS proxy and DHCP/TFTP server
root@ecoli:~# apt-get install dnsmasq
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
dnsmasq
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/16.0 kB of archives.
After this operation, 71.7 kB of additional disk space will be used.
Selecting previously unselected package dnsmasq.
(Reading database ... 429242 files and directories currently installed.)
Preparing to unpack .../dnsmasq_2.75-1_all.deb ...
Unpacking dnsmasq (2.75-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
Setting up dnsmasq (2.75-1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (229-4ubuntu4) ...
root@ecoli:~# cat /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 127.0.0.1
search nimbios.org
root@ecoli:~# dpkg -l | grep dnsmasq
ii dnsmasq 2.75-1 all
Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-base 2.75-1 amd64
Small caching DNS proxy and DHCP/TFTP server
root@ecoli:~#
This is on a machine that was previously running 14.04, and now has a
fresh re-formatted/re-installed 16.04. Under 14.04 this wasn't a
problem. This just started under 16.04. And the contents of my
/etc/network/interfaces hasn't changed from 14.04.
Michael
On 04/27/2016 12:21 PM, msp3k wrote:
> They are specified in /etc/network/interfaces just as you instructed,
> and the dnsmasq-base package is installed. But when dnsmasq is
> installed then resolvconf generates an incorrect /etc/resolv.conf. If I
> remove the dnsmasq package then resolvconf works properly and generates
> the expected contents for /etc/resolv.conf.
>
> This is a new bug with 16.04. It was not present under 14.04, and the
> contents of my /etc/network/interfaces file has not changed.
>
> Michael
>
> On 04/27/2016 12:06 PM, Thomas Hood wrote:
>> Not dnsmasq but dnsmasq-base is pulled in by ubuntu-desktop.
>>
>> If you define your interfaces statically using /etc/network/interfaces
>> then you have to add the nameserver information
>> /etc/network/interfaces on lines like "dns-nameserver 1.2.3.4". See
>> resolvconf(8) for more info.
>>
>> ** Changed in: resolvconf (Ubuntu)
>> Status: New => Incomplete
>>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1575644
Title:
resolvconf doesn't create the correct /etc/resolv.conf file when
static IP addresses are used
Status in resolvconf package in Ubuntu:
Incomplete
Bug description:
By default, when installing ubuntu-desktop (and when installing some
other packages as well), apt will also install dnsmasq as a
dependency. When dnsmasq is installed, and static IP addresses are
used, resolv.conf creates a nearly empty /etc/resolv.conf file. The
file only contains entries for localhost and the search domain. If
static IP addresses are defined in /etc/network/interfaces, then
shouldn't those DNS servers should be included in /etc/resolv.conf
regardless of the presence of dnsmasq?
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Wed Apr 27 08:34:24 2016
InstallationDate: Installed on 2016-04-26 (0 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.3)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1575644/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
