Sidney Markowitz wrote: > use something that combines the pid and id Brain fade... This patch works by matching information that is in the reply packet to information in the query packet, which means it has to use the host name and the packet ID. Duh! Sorry.
Still, we could try some debug log output to determine if the different processes are using the same source ports. I don't see how we could have collisions in the ID unless the source ports are the same. If that's it, we would not have to use the host name to ensure that the reply matches the query if we had a way of making the source ports different across processes. Could you run with debug output that shows the pid, packet ID and source port for the packets that are created in DnsResolver in a run that demonstrates the bug? -- sidney
