NSlookup behavior

Question

_{Friday, July 12, 2019 12:47 PM}

I've noticed some different behavior in how NSLOOKUP works between the Windows version and the BIND version. When I open NSLOOKUP in interactive mode, on both versions, I get back my primary NS DNS name and its IPv4 address. This is where the differences begin. In the interactive prompt, I change my name server via the 'server (name server here)' command.  We have multiple name servers in our network, both BIND and Microsoft DNS. Which server I set doesn't seem to matter as far as results go. The Windows version of NSLOOKUP returns the name of the server, and then the IPv6 address and the IPv4 address in that order. The BIND version of NSLOOKUP returns them in the opposite order, with v4 coming in first (with a #53 appended to the IP), and then the IPv6 address. 

The problem is IPv6 doesn't really work on our network at the moment. When I use the windows version of NSLOOKUP with the IPv6 record first, my queries fail immediately. Wireshark indicates that the query never actually generates any network packets.

When I query a record with the BIND version that received the IPv4 address first, I get the answer back almost immediately with no failures. 

I realize there are several workarounds, such as setting my 'server' command to use an IPv4 address instead of the server name. I can also null-route all my IPv6 traffic and get timeouts instead of failures. 

This behavior seems broken. Is this just a result of the version of NSLOOKUP included in Windows not behaving in the same way as the version of NSLOOKUP in the BIND tools?  

All replies (3)

_{Monday, July 15, 2019 6:24 AM}

Hi,

If both IPv4 and IPv6 are enabled in TCP\IP at the same time, Windows will prefer to use IPv6.

If you don't want to display IPv6 in nslookup, please uncheck the interface in DNS server. 

Or just disable IPv6 in TCP\IP.

Best regards,

Travis

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Tuesday, July 23, 2019 6:18 AM}

Hi,

Just checking in to see if the information provided was helpful.

Please let us know if you would like further assistance.

Best Regards,

Travis

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Tuesday, July 30, 2019 2:29 AM}

Hi,

Was your issue resolved?

If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions.

If no, please reply and tell us the current situation in order to provide further help.

Best Regards,

Travis

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]