FS#33946 - [dnsmasq] does not answer queries on UDP when bind-dynamic is on use.
Attached to Project:
Arch Linux
Opened by Iván De Gyves (FoxBuru) - Wednesday, 20 February 2013, 07:22 GMT
Last edited by Dave Reisner (falconindy) - Friday, 08 March 2013, 20:07 GMT
Opened by Iván De Gyves (FoxBuru) - Wednesday, 20 February 2013, 07:22 GMT
Last edited by Dave Reisner (falconindy) - Friday, 08 March 2013, 20:07 GMT
|
Details
Description:
DNSMasq should allow queries tcp/udp coming from the host to the own host when running on bind-dynamic mode. This configuration is pretty common when using dnsmasq and libvirt with a network configured domain into the xml of the NAT-network of libvirt pool. Additional info: * dnsmasq => 2.65-1 * Sample XML from libvirt default net with domain configured. <network> <name>default</name> <uuid>bb2cf8a2-3d40-4b9e-a187-9b1ca4abd390</uuid> <forward mode='nat'/> <bridge name='virbr0' stp='on' delay='0' /> <mac address='52:54:00:DF:39:76'/> <domain name='v.FoxJR.haus.foxburu.mx'/> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.254' /> <host mac='52:54:00:de:c7:cc' name='radius.v.FoxJR.haus.foxburu.mx' ip='192.168.122.101' /> <host mac='52:54:00:83:6a:64' name='w3.v.FoxJR.haus.foxburu.mx' ip='192.168.122.3' /> </dhcp> </ip> </network> Steps to reproduce: dig @192.168.122.1 +tcp w3 => Actual response from the dnsmasq running with libvirt dig @192.168.122.1 w3 => No response More info and a patch can be retrieved from https://bugzilla.redhat.com/show_bug.cgi?id=904940 |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 08 March 2013, 20:07 GMT
Reason for closing: Won't fix
Additional comments about closing: Please patch this yourself it it matters. The next upstream release is due fairly soon.
Friday, 08 March 2013, 20:07 GMT
Reason for closing: Won't fix
Additional comments about closing: Please patch this yourself it it matters. The next upstream release is due fairly soon.
Comment by
Dave Reisner (falconindy) - Friday,
08 March 2013, 20:06 GMT
I'm not fixing this. It's far from critical and there's a dnsmasq
release in the near future which will include this patch.