Scott:
in the past few days, I've again seen several false "No Reverse DNS"
reports. Each time I confirmed, that MS DNS was timing out on the reverse
DNS, even though it DOES exist. Clearing the cache in MS DNS resolves the
problem. So the underlying problem is of course Microsoft's.
However, in the meantime, Declude should recognize and handle time-outs
properly - but does NOT. Of course, I can't force Declude to look up
specific IP addresses and I can't set myself a test email from the other IP
address - so - I can't produce a debug log for you easily.
Here is a typical DNS query that times out (before the cache was cleared):
> nslookup
> set type=ptr
> 141.153.170.222
Server: maywood-is-0002.webhost.hm-software.com
Address: 63.107.174.65
------------
SendRequest(), len 46
HEADER:
opcode = QUERY, id = 27, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
222.170.153.141.in-addr.arpa, type = PTR, class = IN
------------
DNS request timed out.
timeout was 2 seconds.
timeout (2 secs)
SendRequest failed
Best Regards
Andy Schmidt
Phone: +1 201 934-3414 x20 (Business)
Fax: +1 201 934-9206
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
