I thought it would be good to post this here since others might have
some feedback that would help Declude determine the proper way to go on
this.
I have noted that in Declude 2.x, when an invalid reverse DNS lookup is
found, such as 4.79.67.53 returning "alias =
53.0-127.67.79.4.in-addr.arpa.", Declude would substitute the reverse
DNS lookup of one's own server. This was definitely not desirable, and
this appears to have been changed in 3.x based on some reports. The new
3.x functionality will instead return a null or blank value. I'm not
sure that this is desirable either, though it is better than
substituting the name of one's own server. The reason why this isn't
necessarily good to return a null or blank value is for filtering
purposes (internal and external) and the lingua franca of Declude that
had already been established.
When there is no reverse DNS value, Declude will return "[No Reverse
DNS]", when there is a timeout on the lookup, Declude will return
"(timeout)", but on these invalid lookups, Declude now returns either
null or blank. I'm thinking that it would be useful for Declude to
substitute a value here that identifies the condition, such as "[Invalid
Reverse DNS]".
This is kind of a minor tweak in a way, but it did cause me an issue in
an external app that was expecting to see a value for Reverse DNS. I
could also see it causing confusion and difficulties down the line for
others, and keeping to the format that Scott had established, a
substitution for a value here would be nice to see.
Thanks,
Matt
---
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.
