FS#42228 - [dnsmasq] recursively queries itself when asked for an AAAA record of a DHCP host

Attached to Project: Arch Linux
Opened by Wouter Verhelst (wouter) - Friday, 03 October 2014, 12:59 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 04 November 2014, 12:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dave Reisner (falconindy)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The libvirt network on a local machine started failing after a recent upgrade (last week).

Investigating, it turned out that DNS was no longer functional, and restarting dnsmasq fixed the issue.

An hour later, the problem returned.

I again restarted dnsmasq with the libvirt options, but added the --no-daemon option. After a while, it started producing messages that the maximum number of concurrent DNS requests had been reached. I restarted dnsmasq again, this time adding the -q option (to also log queries); at this point, the following started showing up:

dnsmasq: query[AAAA] opensuse-131-32 from 192.168.122.1
dnsmasq: forwarded opensuse-131-32 to 127.0.0.1
dnsmasq: query[AAAA] opensuse-131-32 from 192.168.122.1
dnsmasq: forwarded opensuse-131-32 to 127.0.0.1

etc. "opensuse-131-32" is the hostname of one of the machines on the libvirt network; i.e., it is a machine that dnsmasq handed out an IPv4 address for. Notice the fact that a quad-A record is asked, however.

Additional info:
* package version: 2.71-1

Steps to reproduce:
* Install libvirt, make sure libvirt default network is started (should start dnsmasq with "--conf-file=/var/lib/libvirt/dnsmasq/default.conf --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper"
* Start a VM, have it do a DHCP request
* Try to resolve the IPv6 address of that VM's hostname more than 150 times.
* Watch dnsmasq explode (sortof)

libvirt's default.conf and libvirt_leasehelper are attached
This task depends upon

Closed by  Dave Reisner (falconindy)
Tuesday, 04 November 2014, 12:46 GMT
Reason for closing:  No response
Additional comments about closing:  If this is still a problem, I'm sure upstream would still like to know about it.
Comment by Dave Reisner (falconindy) - Friday, 03 October 2014, 13:05 GMT
If you suspect a bug in dnsmasq, then please report it upstream: dnsmasq-discuss@lists.thekelleys.org.uk
Comment by Dave Reisner (falconindy) - Saturday, 25 October 2014, 16:41 GMT
Ping -- is this still a problem with 2.72? If so, could you please report this to upstream?

Loading...