http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1605
------- Comment #5 from stephentfisher@xxxxxxxxx 2008-01-11 04:35 GMT -------
(In reply to comment #4)
> With ADNS enabled, at least one problem is that Wireshark doesn't wait for the
> responses before drawing the packet list - it's a little TOO async! So the
> initial render will show mostly IP addresses.
This is intentional to keep DNS lookups from slowing down the packet list
display even the slightest bit.
> A reload will, mostly, correct that. But I still see some IP addresses (e.g.
> 204.9.178.171 = blogs.sixapart.com) that should be able to be resolved, and no
> number of reloads fixes that. Maybe it's overloading the name server (or the
> link??), UDP packets are being dropped, and there's no retry in ADNS?
> Do you want a capture of wireshark loading the capture, or is this enough info
> to go on?
Are the hostnames that are not resolved the same every time? Are you using a
form of Unix or Windows? If on Unix, try looking up the hostnames with the
adnshost program (if installed on your system): adnshost <hostname>. Do they
resolve then?
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.