[166573] in North American Network Operators' Group
Re: Reverse DNS RFCs and Recommendations
daemon@ATHENA.MIT.EDU (Stefan =?utf-8?Q?F=C3=B6rster?=)
Thu Oct 31 01:52:20 2013
Date: Thu, 31 Oct 2013 06:52:04 +0100
From: Stefan =?utf-8?Q?F=C3=B6rster?= <cite+nanog@incertum.net>
To: nanog@nanog.org
In-Reply-To: <D27DF53349E1E94AA9599001CC1C718917A523BC@kw2k8.KWAUTO.PRI>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
* Nolan Rollo <nrollo@kw-corp.com>:
> It seems like the unspoken de facto that mail admins appreciate
> given the IP 203.0.113.15 is
> "203-0-113-15.[type].[static/dynamic].yourdomain.tld". This seems
> perfectly acceptable, it's short, detailed and to the point. Is
> there really anything bad about this?
Mail admins wanting matching forward/reverse DNS and hostnames that
don't "look dynamically generated" is probably more of a human than an
RFC thing: "We used to get a lot of spam from dialup IPs, or IPs
without matching reverse DNS, so let's reject anything that comes from
an IP without FcRDNS and greylist anything with more than X dashes and
Y dots in it's hostname."
Stefan
--X1bOJ3K7DJ5YkBrT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJScfADAAoJEEkf7SxLrpskuBgP/j7Zo+YZp0CYQxoG3BDan3+8
okWNWY6khJZwGXgufmEbXX1IeO/Ic8NyDia81lZfyCBI52hC78XqBoilv/NJz2Zb
2keLCRq/2C8zQqMcYyBV91IIDD/DD1ZH7PmDE3kyw0c1OIRv2DlWVetcrX9mukP3
qgJ8MJlwi+aN0pJnuQLh6NZEEWltoCOd+YPWMuUDv3Kw0+ouHdFqP4TtpfL8fPs5
gHnAKf+IxDkTxYoUTDyVPy8SUe1V4XRnUotbL/h9BjrzisHgPWZJIjc2Y81xv28k
l/ld+GWohWYkkMloX3lDVheCpbuN59CmPg/+9cCExxQRaDsdG7dVuK0dp0qQs2pA
sLGOWqdwsvGaJVrnF9KU7InQYSyS2w0KZ/8+4QY5TSQzdz4cs0TznEuBiiroHPUw
FF0N5gFrP/7vAyTzqUnT0mouC/quQpxfgn+/sDJid81rweM1pC/rSRohhmfLSkkk
Ejz2avSPIY/hdc3gMnm+J1e/I63Ssp70bcZgLPlW22xOgxifpPN/KBuKXoE0BARF
IwfJ5iqBvUfQZpXulMqVjBYJ0GtVEp0drcFeMMIZljTagmxoQJs5uFz1XvSjw3Cj
wIvBFha+jsLbRSs30CALwTdKVRbRoJ2Yvm7yqYyXteO2SN1Bf8iVxSAJo0I4owQs
qYF/I9pAcR4YnQkwAoVS
=VleK
-----END PGP SIGNATURE-----
--X1bOJ3K7DJ5YkBrT--
