On Jun 14, 2010, at 7:03 AM, [email protected] 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 is made to upgrade Windows?
>
> In this discussion, I have not seen any definition/details as to
> what is "broken".
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 line.
nslookup alliance.gd-ais.com ns.azsd01.gd-ais.com
When used in an interactive mode, the same failure occurs.
nslookup
> server ns.azsd01.gd-ais.com
> alliance.gd-ais.com
The response displayed by Windows nslookup in both cases indicate that the
information was obtained from the specified name server. However, if you have
tcpdump running on the name server, you will find that the name server was
never queried.
In each of the above cases, had the name server been queried, the user would
have received two A records for the Internet accessible portal that allows
employees at customer sites, customers, and vendors to access
alliance.gd-ais.com. What was displayed was the internal address for
alliance.gd-ais.com.
--
Merton Campbell Crockett
[email protected]
_______________________________________________
bind-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/bind-users
