Why does not "dig" work?

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Wed Feb 23 07:52:29 UTC 2000


> On Wed, 23 Feb 2000 Mark.Andrews at nominum.com wrote:
> 
> | Date: Wed, 23 Feb 2000 17:49:11 +1100
> | From: Mark.Andrews at nominum.com
> | To: wind at bora.net
> | Cc: bind <bind-users at isc.org>
> | Subject: Re: Why does not "dig" work? 
> | 
> | 
> | 	ns1.pubnetplus.ne.kr is sending back answers from the wrong IP address
> | 	for both UDP and TCP.  Its kernel is broken.
> 
> Is this a kernel thing, or maybe an old BIND version that did not
> care to respond from the interface it received a query on?

	Kernel in this case.  See the TCP traces in the previous message.

	Mark
> 
> I have a similar case here...
> 
> thanks
> 
> | 
> | 	The most probable reason for the different responses is differing
> | 	versions of the resolver library.  Modern resolver libraries block
> | 	answers from the wrong address either at the UDP layer or in the
> | 	library itself.  A new dig and a old nslookup would give this sought
> | 	of responses.
> | 
> | 	Mark
> | 
> | tcpdump -n udp port 53 or icmp
> | tcpdump: listening on se0
> | 17:11:34.610987 130.155.191.233.2207 > 210.220.16.7.53: 44039 A? www.cisco.
> com. (31)
> | 17:11:35.624778 210.220.16.241.53 > 130.155.191.233.2207: 44039 1/2/2 (124)
> [...snip...]
> 
--
Mark Andrews, Nominum Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com



More information about the bind-users mailing list