Bug #4022
closed
Unbound doesn't set 127.0.0.1 in resolv.conf
100%
Description
127.0.0.1 should be first in resolv.conf where unbound is enabled and bound to localhost. line 145 in system.inc. There's an issue with the logic there.
This also needs an additional check - if dnsmasq/unbound aren't listening on port 53, skip adding 127.0.0.1 to resolv.conf to avoid the same breakage that used to happen when not bound to localhost.
Updated by Chris Buechler about 10 years ago
- Status changed from New to Confirmed
Updated by Renato Botelho about 10 years ago
- Status changed from Confirmed to Feedback
- Assignee set to Chris Buechler
The logic there looks correct, and on my tests it added 127.0.0.1 as the first nameserver in resolv.conf when unbound is enabled and configured to bind localhost or all. Do you have a broken system where I can take a look?
Updated by Chris Buechler about 10 years ago
I was wrong on the line where the problem existed. That's fixed now. I also fixed it to ensure it's only in there if the port is 53.
Updated by Chris Buechler about 10 years ago
- % Done changed from 0 to 100
Applied in changeset 97383d2bda23b89da93e2cf31827a3b2aefe9246.
Updated by Chris Buechler about 10 years ago
- Status changed from Feedback to Resolved
confirmed good