Your message dated Tue, 18 Jun 2013 13:27:49 +0800
with message-id <[email protected]>
and subject line Re: Bug#712632: polipo: DNS resolver times out for an existing
domain
has caused the Debian Bug report #712632,
regarding polipo: DNS resolver times out for an existing domain
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
712632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712632
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: polipo
Version: 1.0.4.1-1.1
Severity: important
Polipo appears to timeout on domains that do indeed exist, but only when
dnsQueryIPv6 is not set to "no". If it is, then everything works.
Here is an example when dnsQueryIPv6 is set to "reluctantly":
--------------------8<--------------------
chris@zack:~$ dig cdn.steampowered.com
; <<>> DiG 9.7.3 <<>> cdn.steampowered.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56114
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;cdn.steampowered.com. IN A
;; ANSWER SECTION:
cdn.steampowered.com. 0 IN A 68.142.93.133
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jun 18 00:57:25 2013
;; MSG SIZE rcvd: 54
chris@zack:~$ http_proxy=http://127.0.0.1:8123/ wget -O /dev/null
http://cdn.steampowered.com/
--2013-06-18 00:58:21-- http://cdn.steampowered.com/
Connecting to 127.0.0.1:8123... connected.
Proxy request sent, awaiting response... 504 Host cdn.steampowered.com
lookup failed: Timeout
2013-06-18 00:59:35 ERROR 504: Host cdn.steampowered.com lookup failed:
Timeout.
chris@zack:~$ http_proxy= wget -O /dev/null http://cdn.steampowered.com/
--2013-06-18 01:03:25-- http://cdn.steampowered.com/
Resolving cdn.steampowered.com... 68.142.93.133
Connecting to cdn.steampowered.com|68.142.93.133|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
...
--------------------8<--------------------
After setting dnsQueryIPv6 to "no" and restarting:
--------------------8<--------------------
chris@zack:~$ http_proxy=http://127.0.0.1:8123/ wget -O /dev/null
http://cdn.steampowered.com/
--2013-06-18 01:04:10-- http://cdn.steampowered.com/
Connecting to 127.0.0.1:8123... connected.
Proxy request sent, awaiting response... 301 Moved Permanently
...
--------------------8<--------------------
It looks like this could be the same issue as #540912, but I am not sure.
--
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers
If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/
PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5
------------------------------------------------------------------------
IMPORTANT INFORMATION/DISCLAIMER
This document should be read only by those persons to whom it is
addressed. If you have received this message it was obviously addressed
to you and therefore you can read it.
Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.
This overrides any disclaimer or statement of confidentiality that may
be included on your message.
--- End Message ---
--- Begin Message ---
On Tuesday, 18 June, 2013 01:05 PM, Christopher David Howie wrote:
Package: polipo
Version: 1.0.4.1-1.1
[...]
It looks like this could be the same issue as #540912, but I am not sure.
It probably is. Or it could be 600678. Please try the version from
unstable where both are fixed.
The packages in stable and certainly in oldstable are VERY buggy to the
point I feel it might be better to remove them. Even unstable is only
slowly making it to a better state of affairs. I'm afraid that even the
version in stable is hardly usable in real life and unsupported since I
will not be able to backport all the patches one by one (bugfixes is
what I will concentrate on for unstable for a while, including making
available the latest upstream which contains many bug fixes, I am told).
Bugs in the stable package are basically wontfix, I'm afraid. But this
definitely applies to oldstable. Sorry for the bad news.
--- End Message ---
