The Cisco VPN Client does, indeed, change the Microsoft generated DNS search
list. The Microsoft DNS resolver routines will use the appropriate Microsoft
or Cisco generated search list to resolve names and IP addresses. The problem
is that Microsoft's nslookup is isn't using this nor does it
On 6/13/2010 4:00 PM, Merton Campbell Crockett wrote:
Inspecting the query log on the name server indicates that BIND never
services a request from the system running Microsoft's nslookup tool. In
addition, using tcpdump in controlled tests, I find that Microsoft's
nslookup implementation never
One thing I also learned recently is that the Cisco IPSEC VPN client
dialer hijacks all UDP DNS packets and sends them to the DNS server
handed out by the VPN concentrators. So dig @x.x.x.x and nslookup
foo.bar x.x.x.x queries don't actually go to x.x.x.x. Don't know if
that's in play here but
-bounces+jlightner=water@lists.isc.org
[mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf
Of Niall O'Reilly
Sent: Monday, June 14, 2010 5:08 AM
To: Merton Campbell Crockett
Cc: BIND Users List
Subject: Re: Microsoft's nslookup Implementation Problems
On 13/06/10 23:55, Merton
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
work in a Windows 7 environment after a decision is made to upgrade Windows?
In this discussion, I
On Jun 14, 2010, at 7:03 AM, b19...@anl.gov wrote:
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
work in a Windows 7 environment after a
In article mailman.1794.1276567385.21153.bind-us...@lists.isc.org,
Merton Campbell Crockett m.c.crock...@roadrunner.com wrote:
I identified the problem in my original message. The Windows nslookup
problem involves the failure to send DNS queries to the name server specified
on the command
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
work in a Windows 7 environment after a decision is made to upgrade Windows?
In the past I've
On Jun 13, 2010, at 1:08 PM, Doug Barton wrote:
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
work in a Windows 7 environment after a decision
On 06/13/10 14:08, Merton Campbell Crockett wrote:
On Jun 13, 2010, at 1:08 PM, Doug Barton wrote:
On 06/13/10 13:00, Merton Campbell Crockett wrote:
Microsoft's nslookup is broken. What alternative applications that can
be installed and used in a Windows XP environment that will continue to
On Jun 13, 2010, at 2:21 PM, Doug Barton wrote:
The problem with the erroneous functioning of Microsoft's nslookup.exe
is that it requires a corporate wide change. There are a number of
reasonably intelligent users that assume nslookup.exe is providing them
correct information. I would need
On 06/13/10 15:55, Merton Campbell Crockett wrote:
Providing access to the web-based tools to IT personnel might not be
that big of a challenge;
Excellent!
however, the problem remains: Using nslookup
is an ingrained behavior for the general user.
I would assert that the general user has
12 matches
Mail list logo
