>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.
I think that it may.
In order for Declude to see that an IP address has no reverse DNS entry, it
must actually receive a response back from the DNS server.
>Here is a typical DNS query that times out (before the cache was cleared):
>
> > nslookup
> > set type=ptr
> > 141.153.170.222
What I would recommend is doing this instead:
nslookup
set type=ptr
set timeout=20
141.153.170.222
The "set timeout=20" will tell nslookup to wait up to 20 seconds for a
response, rather than the default 2 second. Declude will wait up to 15
seconds for a response (and if it doesn't get a response, it will send
another query and wait up to another 15 seconds).
My guess is that Microsoft is responding, but it is taking its time to get
the response for some reason (perhaps it has the wrong NS record for the
lookup, tries contacting it, and times out after 5 seconds).
-Scott
---
[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 .
