On Thu, Jun 5, 2008 at 4:17 PM, Andrew McNabb <[EMAIL PROTECTED]> wrote: > That can be tough, though. You can't always control reverse DNS for any > client that might connect. Even if it's your computer that's > connecting, cable modem companies and ISPs aren't always very > DNS-friendly.
I didn't say the DNS record has to be anything specific, it just has to exist. Almost all ISPs have a reverse DNS record for every IP, they commonly indicate the type or location of the address. Case in point (comcast): 176.175.0.24.in-addr.arpa domain name pointer c-24-0-175-176.hsd1.tx.comcast.net. The problem arises usually when a private address is used where no reverse DNS zone is served at all. This means you either need to synchronize a complete hosts list to all machines, or run your own internal DNS server. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
