public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "René Berber" <r.berber@computer.org>
To: cygwin@cygwin.com
Subject: Re: Cygwin DNS lookup utility
Date: Tue, 10 Jun 2008 21:33:00 -0000	[thread overview]
Message-ID: <g2mri4$47i$1@ger.gmane.org> (raw)
In-Reply-To: <17762732.post@talk.nabble.com>

jtriedl wrote:

> LOL.  I should have mentioned that I checked all the obvious permission
> things, and they're all what one would expect:
> 
> (riedl-ibm-x40: /) ll /usr/bin/nslookup.exe
> 60K -rwxr-xr-x 1 riedl Users 60K Jun 10 10:23 /usr/bin/nslookup.exe*
> (riedl-ibm-x40: /) ll /usr/bin/dig.exe
> 72K -rwxr-xr-x 1 riedl Users 72K Jun 10 10:23 /usr/bin/dig.exe*
> (riedl-ibm-x40: /)
> 
> I was speculating that the permission was some windows restriction on
> sending low-level name service requests, but I was hoping someone on this
> list would know more.

ISC's BIND works fine out of the box (no "instructions" followed).  No 
real answer to your question, my guess is that you did something wrong 
(like follow "instructions" for a Microsoft compiler or build in a weird 
file system, not NTFS, perhaps a network share or NFS mounted with no 
execute permission).

$ tar xvf bind-9.5.0.tar.gz
$ cd bind-9.5.0
$ ./configure --enable-threads --with-openssl=yes --with-libtool
$ make
$ make install
$ which dig
/usr/local/bin/dig
$ dig smbserver

; <<>> DiG 9.5.0 <<>> smbserver
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52334
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;smbserver.                     IN      A

;; AUTHORITY SECTION:
.                       8267    IN      SOA     A.ROOT-SERVERS.NET. 
NSTLD.VERISIGN-GRS.COM. 2008061000 1800 900 604800 86400

;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jun 10 16:25:37 2008
;; MSG SIZE  rcvd: 102
-- 
René Berber


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2008-06-10 21:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-08 16:03 David
2008-06-08 16:53 ` Christopher Faylor
2008-06-08 17:13   ` David
2008-06-08 17:14     ` Christopher Faylor
2008-06-08 17:52 ` cuicui
2008-06-08 18:14   ` Mark Geisert
2008-06-08 19:21     ` cuicui
2008-06-08 21:31       ` Christopher Faylor
2008-06-08 22:24         ` cuicui
2008-06-08 20:55   ` Port Bind to Cygwin. $100 David
2008-06-08 21:35     ` Reini Urban
2008-06-08 22:04       ` Christopher Faylor
2008-06-09  0:11         ` Reini Urban
2008-06-11 10:09       ` Yaakov (Cygwin Ports)
2008-06-10 17:56   ` Cygwin DNS lookup utility jtriedl
2008-06-10 19:20     ` Christopher Faylor
2008-06-10 20:49       ` jtriedl
2008-06-10 21:04         ` Christopher Faylor
2008-06-10 21:33         ` René Berber [this message]
2008-06-10 22:39           ` jtriedl
2008-06-09 16:54 ` Andrew Schulman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='g2mri4$47i$1@ger.gmane.org' \
    --to=r.berber@computer.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).