https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5229
Gary Chaulklin <GaryChaulklin@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Enable concurrent DNS name |Enable concurrent DNS name
|resolution error |resolution
--- Comment #2 from Gary Chaulklin <GaryChaulklin@xxxxxxxxx> 2010-09-16 16:00:00 PDT ---
(In reply to comment #1)
> (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.
Sorry - "Enable concurrent DNS name resolution" was intended. I was using
1.2.8 and many previous versions for the past several years. Maybe this a DNS
issue in my shop??? It is a pretty stark, consistent error that I am seeing
for the first time. I'll see if it happens at home with 1.4.0 and at work with
1.2.X as well.
FYI - the error was only on my PC's IP address - all the others looked OK. The
correct IP address was listed for my PC, but with DNS name for a PC belonging
to an employee at a different location. I tried a bunch of things like
flushing DNS, renewing my IP, etc. Nothing helped. Then I turned off Enable
concurrent DNS name resolution and all was well.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.