As n.m. says, on Cygwin res_init() does not populate _res.nsaddr_list if it is using
the Windows resolver. It uses the Windows resolver if either /etc/resolv.conf does
not exist, or /etc/resolv.conf contains options osquery .
Sep 5, 2016 ... Using: Microsoft Windows [Version 10.0.14393] Currently, /etc/resolv.conf is
autogenerated - which is perfect for most situations. I'm annoying, however, and
run a local DNS server on my dev boxes to allow custom DNS ...
Sep 2, 2010 ... The reason for this is because there are no DNS servers specified in Cygwin. Dig
uses the same configuration as DNS would be on a linux system, the
configuration file /etc/resolv.conf. By creating this file and adding your ...
Dec 27, 2016 ... The /etc/resolv.conf configuration file contains information that allows a computer
to convert alpha-numeric domain names into the numeric IP addresses. The
process of converting domain names to IP addresses is called ...
Apr 9, 2019 ...Cygwin uses Windows name resolution, not DNS, unless /etc/resolv.conf exists. I'
ve tried creating /etc/resolv.conf, specifying the VMWare DNS that nslookup uses.
I get exactly the same error messages. ipv6 confuses things.
Jun 27, 2018 ... On Mon, 25 Jun 2018 10:50, johndoe65534 at mail.com said: > On Cygwin '/etc/
resolv.conf' is not needed, as ilustrated by the > below log dirmngr requires '
resolv.conf': Cygwin is Unix emulation on Windows and thus GnuPG ...
Configure /etc/resolv.conf file . I found this problem with debug mode! $ /usr/sbin/
squid.exe -f squid.conf -d 5 -N 2017/02/13 17:47:56| Starting Squid Cache
version 3.3.3 for x86_64-unknown-cygwin... 2017/02/13 17:47:56| Process ID
It's the default behaviour of dig not to use the search-option. From the manual
page: +[no]search Use [do not use] the search list defined by the searchlist or
domain directive in resolv.conf (if any). The search list is not used by default. Edit: