Wireshark-bugs: [Wireshark-bugs] [Bug 11339] Wireshark doesn't change DNS server for name resolu
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 25 Aug 2015 02:11:46 +0000

changed bug 11339


What Removed Added
CC   jeff.morriss.ws@gmail.com

Comment # 3 on bug 11339 from 
(In reply to Daniel from comment #2)
> You are correct with your assumption. To clarify this:
> 
> I'm using Wireshark on a Lenovo Laptop, which I use at home and at work. I
> tested the name resolution at home (102.168.2.0/24), shut it completely down
> (no hibernation) and started it again at work (172.19.0.0/22) where the dns
> information are provided by the work dhcp.

... And after a complete shutdown (where Wireshark and all other processes
exited) you had the DNS problem?

If that's the case I can't see how that could be a Wireshark problem.  The only
way Wireshark can "remember" things from run to run (from one instance of the
running process to the next) is through the preferences and recent files and
DNS servers isn't in the list of things stored in those files.

(The case Guy mentioned involves a library caching some DNS results in memory
while Wireshark is running.  But if Wireshark exits, that cache will be
gone...)

You are receiving this mail because:
  • You are watching all bug changes.