Wireshark-bugs: [Wireshark-bugs] [Bug 11339] Wireshark doesn't change DNS server for name resolu

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 25 Aug 2015 02:40:13 +0000

changed bug 11339


What Removed Added
Status CONFIRMED INCOMPLETE

Comment # 4 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.

Does "the dns information" mean "which DNS server to use", i.e. does that mean
that, when you took it in to work, it was using the DNS server that work's DHCP
server told it to use?

And does this mean that you completely shut down Windows at home (so that
neither Wireshark nor Windows nor anything else was running on the machine),
took the machine to work, *rebooted* it (so that Windows started up again from
scratch), and then started Wireshark from scratch?  And, in that case, did
Wireshark *still* try to use the DNS server for home rather than the one for
work?

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