On 07/30/2013 05:18 PM, Ralf Hildebrandt wrote: > * Eliezer Croitoru <eliezer@xxxxxxxxxxxx>: > >> It's most likely to be the internet DNS infrastructure that is the >> problem compared to local mDNS. >> >> In many cases you can get no response when querying a DNS if you do have >> a route problem for a sec. > > And the routing problems suddenly started when I installed 3.4.0.1? > Well not related to squid directly but yes it can be possible since in the INTERNET there are a lot of packets that just drops.. Also I do not know who is the person in charge of the ROUTING but it can be traced using a simple sampling and some NAGIOS dig and ping checks... >> Once a BGP session ended it takes couple secs or MS to get the path >> correctly. >> >> You can test it using a local DNS server that will be a "proxy" that >> response in any case and then see if the DNS is responding with a >> respond or the route is the problem. > > We're using a local cache on all proxies. DNS cache??? Try to force the DNS server to bind specific port to differentiate the PROXY requests to the DNS requests.. Just suggesting some really good test that can be done easily to minimize the damage to specific points. Eliezer > >> This way all the tests will be done on the local network rather then >> over the INTERNET and then you can ask the next person in the chain in >> order to get a deeper response. >> >> Eliezer >
