<html><body><div style="color:#000; background-color:#fff; font-family:Courier New, courier, monaco, monospace, sans-serif;font-size:10pt"><div style="" class="">Next is an excerpt from squids cache.log, printing some debug output:<br style=""><br style="" class="">2014/08/21 08:24:47| idnsALookup: buf is 40 bytes for dc80.s290.meetrics.net, id = 0x81de<br style="" class="">2014/08/21 08:25:09| idnsRead: FD 6: received 56 bytes from 127.0.0.1.<br style="" class="">2014/08/21 08:25:09| idnsGrokReply: ID 0x81de, 1 answers</div><div style="color: rgb(0, 0, 0); font-size: 13.3333px; font-family: Courier New,courier,monaco,monospace,sans-serif; background-color: transparent; font-style: normal;" class=""><br style="" class="">Here, the response from dnsmasq to resolve dc80.meetrics.net took 32s, which seems to be like a timeout somewhere.<br style="" class=""><br style="" class="">Such behaviour I see with several other domains, all of them advertising
domains. <br style="" class="">Sometimes the servers of which change very often, like dc64.s290.meetrics.net next time, or dc61.s290.meetrics.net etc.<br style="" class=""><br style="" class="">So somehow it seems to be related to some type of load sharing, popular for ads :-).<br style="" class="">Actually, I simply block these servers, but that needs regular update of the blocklist.<br style="" class="">Any suggestion, which type of debugging to do for dnsmasq, to trace down the problem ?<br style="" class=""><br style="" class=""></div></div></body></html>