However, DNSstuff resolves the DNS correctly to secnap2.secnap.net.
It appears as if Declude 1.75 is not resolving PTR CNAMEs correctly? I thought we had fixed that problem in an earlier beta?
This issue was supposed to have been fixed in 1.70 I believe, but it wasn't fully fixed. There is an interim release 1.75i1 at http://www.declude.com/release/175i/declude.exe that takes care of this.
It doesn't happen with normal CNAMEs that appear in DNS lookups (which are often used to delegate IP ranges smaller than a Class C range), but happens when an authoritative server returns both a CNAME and the corresponding PTR record (instead of using the CNAME to refer to another server). There seems to be no logical reason to set up the reverse DNS this way, though.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.
--- [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". The archives can be found at http://www.mail-archive.com.
