Bug 117662 - squid shouldn't require resolv.conf
squid shouldn't require resolv.conf
Product: Fedora
Classification: Fedora
Component: squid (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Stransky
Depends On:
  Show dependency treegraph
Reported: 2004-03-06 13:23 EST by Curtis Doty
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-30 07:47:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Curtis Doty 2004-03-06 13:23:26 EST
According to man 5 resolver:

"On a normally configured system, this file [/etc/resolv.conf] should 
not be necessary.  The only name server to be queried will be on the 
local machine, the domain name is determined from the host name, and 
the domain search path is con-structed from the domain name."

However, squid does not play this way and one must manually add the 
following to squid.conf:


To prevent squid from failing thusly:

2004/03/06 12:15:52| /etc/resolv.conf: (2) No such file or directory
FATAL: Could not find any nameservers.
       Please check your /etc/resolv.conf file
       or use the 'dns_nameservers' option in squid.conf.
Squid Cache (Version 2.5.STABLE3): Terminated abnormally.
Comment 1 Martin Stransky 2005-06-30 07:47:34 EDT
Let's take a look at bug 126557

Note You need to log in before you can comment on or make changes to this bug.