Project

General

Profile

Actions
Copy link

Bug #3655

closed

127.0.0.1 shouldn't be used in resolv.conf if dnsmasq not binding there

Added by Chris Buechler almost 10 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
DNS Forwarder
Target version:
2.2
Start date:
05/14/2014
Due date:
% Done:

0%

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

Description

If the DNS Forwarder settings specify IPs to bind to, and that does not include localhost, resolv.conf should not include 127.0.0.1. Having it there causes DNS delays for lookups from the firewall itself, and that delay is adequately long to make auto-update and packages completely fail as it times out before attempting subsequent resolvers.

Actions
Copy link

Also available in: Atom PDF