On Saturday 23 August 2003 04:07 am, Stephen Turner wrote:
...
> Strange. Nobody has reported anything like this before, and then two this
> week. Thanks, Ken and David for your reports.
I didn't report it because I'm going to set up an external resolver program
when I get around to it anyway, so why waste time trying to figure out what's
going on.
> Unfortunately I can't reproduce it, and I can't see anything obviously
> wrong with the code, so it may be partly OS dependent, although Ken is on
> Linux and David on Solaris.
I think both reports are about Solaris.
One thing I noticed was that I missed "-DHAVE_ADDR_T" when I compiled analog
(5.24).
The other thing is DNS sucks. Query for IP address is not guaranteed to return
any result -- depending on gethosbyaddr() and name server implementation.
Try, for example, 64.68.0.1 (dns3.elan.net). If I look it up by name on our
local ns running BIND9, I get the address back. If I try to look it up by
address I get a "nonexistent domain". On our provider's nameserver query
times out reagrdless: "no response from server".
Anyway, it seems that after a couple of runs my re-compiled analog binary
resolved quite a few addresses: I no longer have just two wedges
("unresolved" and "other") in my org charts.
Dima
--
Backwards compatibility is either a pun or an oxymoron. -- PGN
+------------------------------------------------------------------------
| TO UNSUBSCRIBE from this list:
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| Digest version: http://lists.isite.net/listgate/analog-help-digest/
| Usenet version: news://news.gmane.org/gmane.comp.web.analog.general
| List archives: http://www.analog.cx/docs/mailing.html#listarchives
+------------------------------------------------------------------------
