Comment 7 for bug 1273159

Horses and barn doors since this is an old bug, but I thought I'd weigh-in with an opinion that a fixed 5 second timeout isn't really such a good idea to configure. Imagine a scenario akin to OpenStack where there may be hundreds if not thousands of instances attempting to get their DHCP information. With the time it can take to setup the plumbing, and the possibility of all those queries really bogging-down the dnsmasq or spiking its own plumbing, it would be better to have a backoff on the timeouts akin to what TCP does to avoid congestive collapse. So start at some reasonable (default) minimum and double it on each retry. Or at least increase the timeout by some quantity on each retry if you cannot stomach doubling it.