Reverse DNS for eyeballs?
heasley
heas at shrubbery.net
Fri Apr 21 15:31:12 UTC 2023
Fri, Apr 21, 2023 at 07:37:49AM -0500, Chris Adams:
> Once upon a time, Forrest Christian (List Account) <lists at packetflux.com> said:
> > I have a feeling that I might be stepping into a can of worms by asking
> > this, but..
> >
> > What's the current thinking around reverse DNS on IPs used by typical
> > residential/ small business customers.
>
> I don't see any benefit to programmatically-generated reverse DNS. I
> stopped setting it up a long time ago now. Really, reverse DNS these
> days is mostly only useful for:
>
> - mail servers (where it shows a modicum of control and clue)
> - infrastructure/router IPs (so mtr/traceroute can show useful info)
I view complete DNS coverage to be a basic function. All used addresses
should have forward and matching reverse records. This is not difficult
stuff. Bonus points for including a clli code or similar indicating the
general location of use for uses like network device interfaces, commodity
end-users, etc; also not difficult stuff.
You are tracking your allocations, right? Programmatically generating
your device configurations? So, generate DNS from that same database(s).
More information about the NANOG
mailing list