| Bug ID |
11339
|
| Summary |
Wireshark uses wrong DNS Server
|
| Product |
Wireshark
|
| Version |
1.12.6
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Minor
|
| Priority |
Low
|
| Component |
Common utilities (libwsutil)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.12.6 (v1.12.6-0-gee1fce6 from master-1.12)
Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 17 2015),
with
AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz, with 7988MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
I'm working with two different networks:Ethernet LAN in a 172.19.0.0/22 network
(work) and Wireless in a 192.168.2.0/24 network (home).
For testing purposes, I activated preferences->name resolution->resolve network
(IP) addresses in my home network. Since then, if resolve network addresses is
activated, wireshark uses the home dns (192.168.2.1) server and not the
dns-server which win7 uses (172.19.3.32, checked with ipconfig /all). Option
use an external network name resolver is checked. The problem is reproducable.
You are receiving this mail because:
- You are watching all bug changes.