Attention maintainers making use of minires: I have a new test version, minires-0.98, which interfaces to the built-in Windows resolver, on systems starting with Windows 2000.
The package auto-detects the system it is running on and acts accordingly. However if the file /etc/resolv.conf is readable, the package reverts to contacting the name servers directly (as it does on Win9x and NT4.0). The main reason it's a test package is because of the mapping of the Windows error codes to resolver error codes. It's hard to cover all possible cases. The test package writes to stderr when it finds unexpected outcomes. I would appreciate it receiving feedback if you use this package. Because it's a test version the setup.hint's appear below. Pierre http://mysite.verizon.net/minires-0.98-1/minires/minires-0.98-1.tar.bz2 http://mysite.verizon.net/minires-0.98-1/minires/minires-0.98-1-src.tar.bz2 http://mysite.verizon.net/minires-0.98-1/minires/setup.hint http://mysite.verizon.net/minires-0.98-1/minires-devel/minires-devel-0.98-1. tar.bz2 http://mysite.verizon.net/minires-0.98-1/minires-devel/setup.hint # minires-0.98-1 setup.hint sdesc: "A simple synchronous non caching stub resolver." ldesc: "A simple synchronous non caching stub resolver providing the basic functionality of bind. It interfaces to Windows to find the DNS servers. On Windows 2000+, it can interface with the built-in Windows resolver." test: 0.98-1 category: Libs requires: cygwin # minires-devel-0.98-1 setup.hint sdesc: "A simple synchronous non caching stub resolver." ldesc: "Development package for a simple synchronous non caching stub resolver providing the basic functionality of bind. It interfaces to Windows to find the DNS servers. On Windows 2000+, it can interface with the built-in Windows resolver." test: 0.98-1 category: Libs Devel requires: cygwin