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: Mon, 06 Jul 2015 07:03:07 +0000

changed bug 11339


What Removed Added
Status UNCONFIRMED INCOMPLETE
Component Common utilities (libwsutil) Dissection engine (libwireshark)
Summary Wireshark uses wrong DNS Server Wireshark doesn't change DNS server for name resolution if network configuration changes
Ever confirmed   1

Comment # 1 on bug 11339 from 
I infer, from what you said in the question on ask.wireshark.org:

    I'm working with two different networks:Ethernet LAN in a 172.19.0.0
network (work) and Wireless in a 192.168.2.0 network (home).

that you took your machine from home to work, but it didn't switch to using the
work DNS server - it continued to use the home DNS server.  If that is *not*
the case, please indicate that; until then, I'll assume that is the case.

Given that:

As the build information indicates, your Wireshark is using c-ares to resolve
IP addresses to host names; from a quick look at the c-ares code code, it
should use the same DNS servers that the system's DNS resolver does, although
it might not re-check for the DNS servers to use if the machine moves from one
network to another.

We might need to catch whatever events Windows delivers, if any, to indicate
that the network configuration has changed in a way that might indicate a
change in DNS server, and re-initialize c-ares when that happens.

(We probably want to do that on other OSes, e.g. OS X, as well.)

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