Your problem or Cygwin's ?????

Below is a cut/paste of the results of two different nslookups executed as admin under Command Prompt (cmd). Almost identical results when executed on Cygwin. Cygwin's nslookup is distributed with its bind9 package. My question is whether this is a bind9 problem or did the Cygwin folks mismanipulate their package software?

> where nslookup
C:\Windows\System32\nslookup.exe
C:\cygwin64\bin\nslookup.exe

 > C:\Windows\System32\nslookup.exe -query=any andromeda.cs.purdue.edu ns3.purdue.edu
Server:  ns3.purdue.edu
Address:  128.210.224.226

andromeda.cs.purdue.edu internet address = 128.10.19.24
cs.purdue.edu   nameserver = ns1.rice.edu
cs.purdue.edu   nameserver = ns3.purdue.edu
cs.purdue.edu   nameserver = harbor.ecn.purdue.edu
cs.purdue.edu   nameserver = ns4.purdue.edu
cs.purdue.edu   nameserver = pendragon.cs.purdue.edu
cs.purdue.edu   nameserver = ns2.rice.edu
ns1.rice.edu    internet address = 128.42.209.32
ns2.rice.edu    internet address = 128.42.178.32
ns3.purdue.edu  internet address = 128.210.224.226
ns4.purdue.edu  internet address = 128.210.224.234
harbor.ecn.purdue.edu   internet address = 128.46.154.76
pendragon.cs.purdue.edu internet address = 128.10.2.5
ns3.purdue.edu  AAAA IPv6 address = 2001:18e8:800:200::a
ns4.purdue.edu  AAAA IPv6 address = 2001:18e8:800:201::a

 > C:\cygwin64\bin\nslookup.exe -query=any andromeda.cs.purdue.edu ns3.purdue.edu
socket.c:5916: connect(128.210.224.226#53) 116/Connection timed out
/usr/bin/nslookup: isc_socket_connect: unexpected error
'''

-- Thanks,
--    aabatpurdue