On 7/6/06, cuicui <cuicui.o...@free.fr> wrote:
Denny wrote:
> On 7/6/06, dny <mail2...@gmail.com> wrote:
>> On 7/6/06, Henrik Nordstrom <hen...@henriknordstrom.net> wrote:
>> > ons 2006-07-05 klockan 18:08 +0700 skrev dny:
>> > > i have this weird problem with squid on a clean install ipcop 1.4.10
>> > >
>> > > there are lots of website give out error:
>> > > The dnsserver returned:
>> > > No DNS records
>> > >
>> > > ping to the domain from ipcop box gives unknown host error.
>> > >
>> > > but, when i ping the domain name from client pc, it gives out good
>> reply.
>> > > and when i disable the proxy, the website opened up fine.
>> >
>> > Most likely the two is using different DNS servers. The one used by the
>> > clients working, but the one used by Squid & ipcop broken...
>> > check /etc/resolv.conf.
>> >
>> > Regards
>> > Henrik
>> >
>> >
>> > -----BEGIN PGP SIGNATURE-----
>> > Version: GnuPG v1.4.4 (GNU/Linux)
>> >
>> > iD8DBQBErAFuB5pTNio2V7IRAujbAKCjKmaTTIpXn/bWF308iLb/FV/TsACgx2Hh
>> > 3BOAGu+Ht3K7HtAxiC8LPCg=
>> > =oxk9
>> > -----END PGP SIGNATURE-----
>> >
>> >
>> >
>>
>> /etc/resolv.conf only have one ip, that is 127.0.0.1
>> because it's using dnsmasq to resolve the domain name.
>>
>> restarting the ipcop will fix the problem for few hours.
>> then it occurs again...
>>
>> i think maybe the problem is with dnsmasq not powerful enough on a
>> busy proxy?
>>
>> i'm adding my isp dns into /etc/resolv.conf and we'll see if problem
>> fixed or not....
>>
> adding isp's dns into /etc/resolv.conf do not solve my problem.
> the error still happening.
>
> any idea?
I had the same error: some website names couldn't be resolved by squid
and some of my ACL (mostly srcdom_regex) didn't work that good.
I tried to launch some lookup using "host" and figured that it was
definitively a dnsmasq issue.
I *suppressed* "127.0.0.1" from my resolv.conf i put my isp's DNS and
everything works fine. That's not a big issue for me because i mostly
use the DHCP side of dnsmasq.
I'm using Debian Sarge with Squid 2.5.14 compiled by hand and the
official debian package for dnsmasq, sorry i can't give more usable
information (maybe this is a negative-cache problem?).
Nicolas
tried remove 127.0.0.1 from /etc/resolv.conf. same problem.
so, the problem maybe not related to dnsmasq
tried insert my isp dns into squid.conf. problem still.
tried dns_children 32 but produce error?
try negative_dns_ttl 1 minutes. better result.
but sometimes still have to refresh to get the page displayed.
any better solution?
rgds,
dny
--- http://bloglines.com/public/bacaan --- harini udah baca blom?
... they look but do not see and hear but do not listen or understand. Mat 13:13
... but that which cometh out of the mouth, this defileth a man. Mat 15:11