Project

General

Profile

Actions
Copy link

Bug #4022

closed

Unbound doesn't set 127.0.0.1 in resolv.conf

Added by Chris Buechler about 10 years ago. Updated about 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Chris Buechler
Category:
DNS Resolver
Target version:
2.2
Start date:
11/17/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:

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.

Actions
Copy link

Also available in: Atom PDF