phil curb wrote:
I was getting this error..
using windows port of squid
Seems it was not getting DNS servers properly.
had to set both of them dns_nameservers in squid.conf
then it worked.
the short story with answer is
I did ipconfig /all
it shows 10.0.0.138 as DNS server, and 192.168.0.1 as
my "Gateway" i.e. router. But the same device, like
most NAT routers, it is a DNS server too.
As you can see, my NAT router is slifghtly weird like
that. Speedtouch 546. It seems to have 2 ip addresses.
I can http to 192.168.0.1 or 10.0.0.138 , and get to
the router interface.
DNS worked, I can browse, and wireshark showed that it
was working. It uses UDP not TCP. And it showed
source dest
DNS query 192.168.0.2 --> 10.0.0.138
DNS response 192.168.0.1 --> 192.168.0.2
as you can see.. the query goes to one DNS ip, the
response comes from the other one. Maybe that is part
of teh reason for a problem.. In that it needed to
know Both DNS server ips.
I reckon squid was only getting 10.0.0.138 as DNS
server and that was not enough.
When I did dns_nameservers 192.168.0.1 10.0.0.138
it worked.
I knew DNS servers were working because I could browse
- when not using the squid peoxy. Now I can browse
with since i fixed it up.
Nope. You applied a hack work-around to tell squid which of the two
available DNS is the working one (192.168.0.1 first in the config).
You should fix your router config to send out the correct DNS info to
clients connecting to it. At present they are getting 10.0.0.138, and if
you are lucky maybe 192.168.0.1 as secondary.
This tends to be a problem with local DNS server (yay the geekdom!) vs.
home-user ADSL boxes. And I do mean 'vs.', theres a minor DNS-config war
going on at DHCP allocation time.
If you are not actively using the router as a properly configured DNS
relay to your upstream external source, you should turn that bit off and
set its DNS server details to be the internal / actual DNS server.
Amos
