Enhancement #3220

« Previous | Next »

Dnsmasq: drop bind-interfaces implementation

Added by Giacomo Sanchietti about 6 years ago. Updated about 6 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:<multiple packages>
Target version:v6.6
Resolution: NEEDINFO:No

Description

Using bind-interfaces option brings many problems since dnsmasq doesn't listen on 0.0.0.0: if a new interface is created (eg. OpenVPN tunnel), dnsmasq server needs to be restarted.

But this option has been added to permit the use of libvirt with DHCP enabled on virbr0 (default NATted network).
This configuration is not used and hardly maintainable in a server-configuration, so we can (almost) safely remove it.

Proposed solution:
  • remove bind-interfaces option from dnsmasq.conf
  • drop default libivrt virbr0 configuration

Related issues

Related to NethServer 6 - Bug #3185: DNS name resolution from openvpn client CLOSED

Associated revisions

Revision 0781646c
Added by Giacomo Sanchietti about 6 years ago

dnsmasq.conf: remove bind-interfaces option. Refs #3220

Revision b5bd6a21
Added by Davide Principi over 5 years ago

Content filter builtin rules [italiano]. Refs #3220

History

#1 Updated by Giacomo Sanchietti about 6 years ago

  • Category set to <multiple packages>
  • Status changed from NEW to TRIAGED
  • Target version set to v6.6
  • % Done changed from 0 to 20

#2 Updated by Giacomo Sanchietti about 6 years ago

  • Related to Bug #3185: DNS name resolution from openvpn client added

#3 Updated by Giacomo Sanchietti about 6 years ago

  • Status changed from TRIAGED to ON_DEV
  • Assignee set to Giacomo Sanchietti
  • % Done changed from 20 to 30

#4 Updated by Giacomo Sanchietti about 6 years ago

  • Status changed from ON_DEV to MODIFIED
  • % Done changed from 30 to 60

#5 Updated by Giacomo Sanchietti about 6 years ago

  • Status changed from MODIFIED to ON_QA
  • Assignee deleted (Giacomo Sanchietti)
  • % Done changed from 60 to 70
Packages in nethserver-testing:
  • nethserver-dnsmasq-1.4.6-1.1.g0781646.ns6.noarch.rpm
  • nethserver-libvirt-1.0.0-1.3.g4329560.ns6.noarch.rpm
Test case
  • In a clean system install nethserver-libvirt and nethserver-dnsmasq
  • Check there are two instanced of dnsmasq: one from libvirt and one is the system DNS server
  • Check system dnsmasq listens on 0.0.0.0
  • Check dnsmasq instance from libvirtd it's not running

#6 Updated by dz0 0te about 6 years ago

  • Assignee set to dz0 0te

#7 Updated by dz0 0te about 6 years ago

  • Status changed from ON_QA to VERIFIED
  • Assignee deleted (dz0 0te)
  • % Done changed from 70 to 90

System and Package Version installed
VM KVM - Clean install of Nethserver 6.6 fully updated
Package Installed: nethserver-dnsmasq-1.4.6-1.ns6.noarch, nethserver-libvirt-1.0.0-1.ns6.noarch
Other Package Group installed: none

Test Original Problem
Enhancement
as per test case, after the installation two instances of dnsmasq are active

Install Updated Package

yum --enablerepo=nethserver-testing update nethserver-dnsmasq-1.4.6-1.1.g0781646.ns6 nethserver-libvirt-1.0.0-1.3.g4329560.ns6

Test Results after update
All ok
- dnsmaq instance from libvirtd is no more running
- netstat -anp | grep 53 

tcp        0      0 0.0.0.0:53                  0.0.0.0:*                   LISTEN      14165/dnsmasq       
tcp        0      0 :::53                       :::*                        LISTEN      14165/dnsmasq       
udp        0      0 0.0.0.0:53                  0.0.0.0:*                               14165/dnsmasq       
udp        0      0 :::53                       :::*                                    14165/dnsmasq

Note
...

#8 Updated by Giacomo Sanchietti about 6 years ago

  • Status changed from VERIFIED to CLOSED
  • % Done changed from 90 to 100
Released in nethserver-updates:
  • nethserver-dnsmasq-1.4.7-1.ns6.noarch.rpm
  • nethserver-libvirt-1.0.1-1.ns6.noarch.rpm

Also available in: Atom PDF