full-disclosure - Reverse dns

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <559C0D98F49C6D8CFE5197D8@utd49554.utdallas.edu>
From: pauls at utdallas.edu (Paul Schmehl)
Subject: Reverse dns

--On Thursday, March 10, 2005 11:35:10 AM -0500 Dale Babiy 
<DaleB@...WWTS.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Rfc1912 section 2.1 says:
>
>    "Every Internet-reachable host should have a name.  The
> consequences
>    of this are becoming more and more obvious.  Many services
> available
>    on the Internet will not talk to you if you aren't correctly
>    registered in the DNS.
>
>    Make sure your PTR and A records match.  For every IP address,
> there
>    should be a matching PTR record in the in-addr.arpa domain.

This pretty much settles it for me.  I think I win this argument.

Thanks for all the help from everyone that posted useful responses.

Paul Schmehl (pauls@...allas.edu)
Adjunct Information Security Officer
The University of Texas at Dallas
AVIEN Founding Member
http://www.utdallas.edu