Actions
Bug #3655
closed
127.0.0.1 shouldn't be used in resolv.conf if dnsmasq not binding there
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.
Updated by Jim Pingle almost 10 years ago
- Status changed from New to Feedback
This should already be OK on 2.2 after bd5737dc22b0e52a52e84fc2d9d1193deb43811d
Updated by Chris Buechler almost 10 years ago
ah thanks, haven't tried on 2.2 yet, saw #3455 and remembered hitting that with a customer last week.
Updated by Chris Buechler over 9 years ago
- Status changed from Feedback to Resolved
Actions