On Mon, Aug 25, 2003 at 01:36:31PM -0500, Dimitri Maziuk wrote: > 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.
No, my report was about RedHat9. > > 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". When I query for this IP I get a non-existant domain, not no response. [EMAIL PROTECTED] ken]$ host 64.68.0.1 Host 1.0.68.64.in-addr.arpa not found: 3(NXDOMAIN) [EMAIL PROTECTED] ken]$ dig ANY dns3.elan.net ; <<>> DiG 9.2.1 <<>> ANY dns3.elan.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15212 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 3 ;; QUESTION SECTION: ;dns3.elan.net. IN ANY ;; ANSWER SECTION: dns3.elan.net. 172726 IN A 64.68.0.1 This means that the DNS administrator forgot to set up a reverse entry for this IP address. There are many domains just like this all over the net. My observation came from a DNS that was improperly configured; it looped. I'm sure there are quite a few of these, too. However it shouldn't bork Analog. Whatever the server is returning appears to cause Analog to no longer do the lookups. Maybe it's a DNS implementation problem. Just looked at my dnscache.txt file and found that 98% of the file is unresolved IPs. [EMAIL PROTECTED] analog]$ wc -l dnscache.txt 65815 dnscache.txt [EMAIL PROTECTED] analog]$ grep "*" dnscache.txt | wc -l 64648 [EMAIL PROTECTED] analog]$ Stephen, is there anything I can do to help troubleshoot this? -- Ken Schweigert, Network Administrator Byte Productions, LLC http://www.byte-productions.com +------------------------------------------------------------------------ | 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 +------------------------------------------------------------------------
