© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
eee2d0b
(Get the code!)
In some specific context that I currently cannot identify (i.e. happens everytime on my server but never in VMs), after a reboot, squid-deb-proxy fails to resolve DNS entries for URL that it needs to service. The problem seems systematic on the hardware that I have.
Release : Trusty (squid-
Test :
1) Reboot squid-deb-proxy server
2) From some client, issue :
$ telnet {squid-
GET http://
Trying 192.168.1.11...
Connected to avogadro.
Escape character is '^]'.
HTTP/1.1 503 Service Unavailable
Server: squid/3.3.8
Mime-Version: 1.0
Date: Tue, 19 May 2015 14:21:51 GMT
Content-Type: text/html
Content-Length: 3287
X-Squid-Error: ERR_DNS_FAIL 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from squid-deb-proxy
X-Cache-Lookup: MISS from squid-deb-
Via: 1.1 squid-deb-proxy (squid/3.3.8)
Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://
<html><head>
<meta http-equiv=
<title>ERROR: The requested URL could not be retrieved</title>
<style type="text/
/*
Stylesheet for Squid Error pages
Adapted from design by Free CSS Templates
http://
Released for free under a Creative Commons Attribution 2.5 License
*/
...
<div id="content">
<p>The following error was encountered while trying to retrieve the URL: <a href="http://
<blockquote id="error">
<p><b>Unable to determine IP address from host name <q>fr.archive.
</blockquote>
<p>The DNS server returned:</p>
<blockquote id="data">
<pre>No DNS records</pre>
</blockquote>
<p>This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct.</p>
<p>Your cache administrator is <a href="mailto:
<br>