Wireshark-bugs: [Wireshark-bugs] [Bug 5229] Enable concurrent DNS name resolution error
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Thu, 16 Sep 2010 15:07:09 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5229

--- Comment #1 from Stephen Fisher <steve@xxxxxxxxxxxxxxxxxx> 2010-09-16 16:07:08 MDT ---
(In reply to comment #0)

> If I turn ON "Enable concurrent DNS name resolution error", my PC resolves to
> the wrong DNS entry.  This is new with 1.4.0.

Are you referring to "enable concurrent DNS name resolution" option in the name
resolution preferences?  I'm not aware of it ending with "error"

> All I have to do is turn OFF "Enable concurrent DNS name resolution error" and
> I get the right DNS entry name for my PC.
> 
> I think this is a major issue due to the confusion it may cause.

With concurrent DNS resolution turned on, the c-ares library does the DNS
lookups and may be doing it differently than the built in OS functions (for
example, something like contacting DNS servers directly instead of using a
local 'hosts' file first) whereas turning it off uses the normal operating
system DNS resolution routines.

Which version of Wireshark were you using before?  We used to use the ADNS
library, but now we use c-ares for concurrent (asynchronous) DNS resolution. 
This may be why the new version isn't working the same way.

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.