Justin Mason wrote, On 2/5/07 1:53 AM: > [no bug number?] Sidney's DNS-on-win32 issue? is this still a bug?
My satellite internet connection went down completely and I couldn't test more. Now that it's back I haven't had a chance to test again. The last time IPSTAR had major downtime here when it came back I had similar strange ongoing problems disappear, so I won't be surprised if my DNS behaves better the next time I test. I did decide that if other people on more reasonable connections don't see the same DNS behavior than it isn't worth making a priority, and may not even be worth calling a bug. I'll keep looking at this just because it is a challenging problem. Oh, by the way, I don't think that the hard coded "20" in the async code is a problem. For it to trigger an abort there has to be 20 seconds during which there are no DNS replies coming in at all. The flakiness that I am seeing results in all DNS replies being lost after the first N queries, but I've never seen straggler replies showing up that long after the previous reply and there are always some replies coming back sooner than 20 seconds. If someone has a setup in which it takes more than 20 seconds to get any DNS query answered than they probably do not want to be running network tests in the first place. -- sidney
