dnsmasq cache-size is hardcoded to 10000
Bug #1619422 reported by
BadBrainJohnson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| dnsmasq (Ubuntu) |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
Most people won't run into this problem, but if you use a very large hosts-file (like this one here: http://
As there is no indication of this arbitrary limit , you might end up wondering: why the hell is dnsmasq not caching anything?
The value was probably put there to save resources if dnsmasq runs on an embedded system and users who need a bigger cache size can setup their patched instance of dnsmasq, but there should be at least some kind of warning in the default config file.
Revision history for this message
| Robie Basak (racb) wrote | #1 |
| tags: | added: need-upstream-report |
| Changed in dnsmasq (Ubuntu): | |
| status: | New → Won't Fix |
| importance: | Undecided → Low |
To post a comment you must log in.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
This sounds like something that should be decided upon by the upstream dnsmasq project, and not in Ubuntu directly. Could you check validity with their current latest release, and if still relevant, file a bug with them please?
Since this behaviour appears to be intentional, I'm marking this bug Won't Fix for Ubuntu, as I don't think we should patch this. If upstream decide to change behaviour, then this can change.