>> The system resolver is blocking, meaning that Polipo hangs during a
>> DNS lookup.
> It is important to note that I've asked for this to be set to
> 'happily'.
> This means polipo should use its own resolver first and _then_ fallback
> to using the system one.
What you suggest will cause polipo to hang every time a user mis-types
a URL.
> In the common case, this has no impact for Debian users.
Sorry, Anand, but I don't think that having a web proxy hang is ``no
impact''. What you suggest allows every user to DOS a running proxy
just by sending requests for random URLs.
> I am using a local DNS server (bind as it happens) but it is not
> appropriate to (nor easy) to have bind override the returned information
> for a single host entry in a non-local zone.
Why is it ``not appropriate''? (If you find it ``not easy'', please
file a bug against bind; it's definitely trivial with pdnsd.)
People are abusing the implementation-specific behaviour of the glibc
resolver (which is modelled after the SunOS resolver), which ends up
biting them when they use software that uses a different resolver
(e.g. Polipo, which has its own resolver, or adns). The solution is
not to rely on glibc behaviour; it is to use a local recursive name
server that is authoritative for your local zones.
If you disagree with the above, another solution to your problem would
be to have polipo parse /etc/hosts on its own, and include the data
gathered therein in its local database. I will gladly accept patches
to Polipo that do that (assuming the licensing is compatible, of course).
Juliusz
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
