Re: [squid-users] TCP-MISS 503 for wrong destination ip

On Tuesday 24 November 2015 at 14:31:15, Ahmad Alzaeem wrote: > The DNS is not broken , it will resolve some websites to ip address of > squid and other websites will rslve to other ip That sounds pretty broken to me (unless the Squid machine really is the web server for those sites whose hostna

Re: [squid-users] TCP-MISS 503 for wrong destination ip

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 24.11.15 19:31, Ahmad Alzaeem пишет: > Ok > > > 1. Have you fixed DNS so that clients are now resolving the correct addresses for destination servers? > No , the issues will not be solved and will always dns resolve the ip of websites to the ip

Re: [squid-users] TCP-MISS 503 for wrong destination ip

Ok 1. Have you fixed DNS so that clients are now resolving the correct addresses for destination servers? No , the issues will not be solved and will always dns resolve the ip of websites to the ip address of squid ( http & https requestst with the wrong ds tip will hit squid) Again , I want

Re: [squid-users] TCP-MISS 503 for wrong destination ip

On Tuesday 24 November 2015 at 13:34:51, Ahmad Alzaeem wrote: > Well , what I have done is : > > I configured squid http_port xx and http_port xxy intercept > > And uses iptables to redirect http & https to squid ports 1. Have you fixed DNS so that clients are now resolving the correct addresse

Re: [squid-users] TCP-MISS 503 for wrong destination ip

.org] On Behalf Of Antony Stone Sent: Tuesday, November 24, 2015 3:18 PM To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] TCP-MISS 503 for wrong destination ip On Tuesday 24 November 2015 at 13:13:17, Ahmad Alzaeem wrote: > Guys I understand that > > The question is bein

Re: [squid-users] TCP-MISS 503 for wrong destination ip

om: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On > Behalf Of Antony Stone Sent: Tuesday, November 24, 2015 2:42 PM > To: squid-users@lists.squid-cache.org > Subject: Re: [squid-users] TCP-MISS 503 for wrong destination ip > > On Tuesday 24 November 2015 at 12:22:4

Re: [squid-users] TCP-MISS 503 for wrong destination ip

Subject: Re: [squid-users] TCP-MISS 503 for wrong destination ip On Tuesday 24 November 2015 at 12:22:40, Ahmad Alzaeem wrote: > Hi Devs , > > I have a server that send to squid http/https with wrong destination > ips It has already been recommended that you fix your DNS so t

Re: [squid-users] TCP-MISS 503 for wrong destination ip

On Tuesday 24 November 2015 at 12:22:40, Ahmad Alzaeem wrote: > Hi Devs , > > I have a server that send to squid http/https with wrong destination ips It has already been recommended that you fix your DNS so that it works correctly / normally. > So assume I want to open google > > The reques

Re: [squid-users] TCP-MISS 503 for wrong destination ip

In the case of obviously faulty DNS you can, for example, set up your own caching DNS (for example, Unbound), which takes data from a known clean source - for example, by using DNSCrypt and, possible, with DNSSEC validation. And specifying it as a source of information for Squid's name resolvin

Re: [squid-users] TCP-MISS 503 for wrong destination ip

The reason may be, for example, in the DNS cache poisoning. Or the transparent interception of DNS requests. In either case, the need to solve various actions and they are not connected with the SQUID. 24.11.15 17:22, Ahmad Alzaeem пишет: Hi Devs , I have a server that send to squid http/htt

Re: [squid-users] TCP-MISS 503 for wrong destination ip

We do not know and can not know why the server sends such a request. There are only assumptions of varying degrees of reliability. SQUID configuration in this case is absolutely not enough to give a reasonable answer. If the problem is DNS - then what's the Squid? 24.11.15 17:22, Ahmad Alzaee

[squid-users] TCP-MISS 503 for wrong destination ip

Hi Devs , I have a server that send to squid http/https with wrong destination ips So assume I want to open google The request hit the squid with https/http packet with payload www.google.com with ds tip 10.0.0.1 not the real ds tip of google like 74.125.x.x