This is a static archive of our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

What is “Use External Network Name Resolver” setting?

0

I noticed a new setting on the Name Resolution menu of Wireshark 1.9.0 development versions called "Use External Network Name Resolver." It was enabled by default. What is the purpose of this setting? On my system, enabling this setting seems to result in Wireshark making DNS PTR queries even when View > Name Resolution > Enable for Network Layer is unchecked.

asked 09 Jul '12, 19:53

Jim%20Aragon's gravatar image

Jim Aragon
7.2k733118
accept rate: 24%


One Answer:

0

Please see https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7380 in short make it possible to select if name resolution is to be made trough DNS lookups or not.

answered 09 Jul '12, 20:54

Anders's gravatar image

Anders ♦
4.6k952
accept rate: 17%

So, if I understand correctly:

View > Name Resolution > Enable for Network Layer should determine IF name resolution is done.

View > Name Resolution > Use External Name Resolver should determine HOW name resolution is done.

So no Layer 3 name lookups should be done if "Enable for Network Layer" is unchecked, regardless of whether "Use External Name Resolver" is checked or not?

Am I seeing a bug in this new feature? When I enable "Use External Name Resolver," I see reverse DNS lookups even though "Enable for Network Layer" is unchecked.

(09 Jul '12, 21:15) Jim Aragon

Yes looks like it.

(09 Jul '12, 21:16) Anders ♦

Judging from the discussion on bugs.wireshark.org, this is still under active development. Should I file a bug report, or wait until the initial implementation settles down?

(09 Jul '12, 21:24) Jim Aragon

"Should I file a bug report, or wait until the initial implementation settles down?"

The answer to that question is "no". :-) You should comment on the existing bug, as it's not closed yet.

(09 Jul '12, 21:49) Guy Harris ♦♦

The new preference wasn't being followed when translating hostnames into IP addresses. That's fixed in r43647.

(10 Jul '12, 08:06) JeffMorriss ♦