[76090] in North American Network Operators' Group
Re: is reverse dns required? (policy question)
daemon@ATHENA.MIT.EDU (Robert Hayden)
Wed Dec 1 12:28:32 2004
Date: Wed, 01 Dec 2004 11:27:54 -0600
From: Robert Hayden <rhayden@doit.wisc.edu>
In-reply-to: <20041201171420.GJ32264@arctic.org>
To: "J.D. Falk" <jdfalk@cybernothing.org>
Cc: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
Besides, if customers "need" it to make their mail work, choosing not to
do it will be a good indication to your customers that another provider
might be more supportive.
Basic non-custom reverse DNS on everything is a "good thing" to put in
place regardless.
- Robert
J.D. Falk wrote:
> On 12/01/04, Greg Albrecht <gba@undef.net> wrote:
>
>
>>are we obligated, as a user of ARIN ip space, or per some BCP, to
>>provide ad-hoc reverse dns to our customers with-out cost, or without
>>financial obligation.
>
>
> From a purely network operations perspective: YES, every IP
> address should have matching forward & reverse DNS. That's been
> beyond best practices and into the "everybody does it unless
> they're really stupid" realm for well over a decade.
>
> Reverse DNS has only become /more/ important as spam-blocking
> efforts noticed the strong correlation between networks too lazy
> to maintain reverse DNS, and networks too lazy or evil to care
> if they were hosting spammers.
>
> As for the finances...that's up to you, but I've never before
> heard of a provider who charged extra for it.
>
