> I would say the absence of reverse DNS tells useful info to receiving
> MTAs - to preferably not accept.
yep
.
On 22/04/2023 16:00, nanog-requ...@nanog.org wrote:
[...]
[..] 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)
- Peers in an Internet eXchange Point
On Fri, 21 Apr 2023 at 20:44, Jason Healy via NANOG wrote:
> This is not intended as snark: what do people recommend for IPv6? I try to
> maintain forward/reverse for all my server/infrastructure equipment. But
> clients? They're making up temporary addresses all day long. So far, I've
>
We actually manually list our customer ranges in pbl, or at least used to.
Probably something else that I need to check on.
On Fri, Apr 21, 2023, 8:04 AM Lukas Tribus wrote:
> Hello,
>
>
> without PTRs you will probably get your prefixes listed in things like
> Spamhouse PBL. So adding the
Once upon a time, heasley said:
> I view complete DNS coverage to be a basic function. All used addresses
> should have forward and matching reverse records.
But why? It's not like anybody can trust what's in a reverse DNS
string, even if it has matching forward. If I'm looking for
> I view complete DNS coverage to be a basic function. All used addresses
> should have forward and matching reverse records.
This is not intended as snark: what do people recommend for IPv6? I try to
maintain forward/reverse for all my server/infrastructure equipment. But
clients? They're
Fri, Apr 21, 2023 at 07:37:49AM -0500, Chris Adams:
> Once upon a time, Forrest Christian (List Account)
> 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
> >
Hello,
without PTRs you will probably get your prefixes listed in things like
Spamhouse PBL. So adding the correct PTR for a mailserver may not be
enough, as services like that love to classify entire IP blocks. Of
course Spamhaus provides the tools to fix this issue. But what if
there are 4 - 5
On 4/21/23 14:37, Chris Adams wrote:
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)
-
On 4/21/23 15:02, Frank Habicht wrote:
I would say the absence of reverse DNS tells useful info to receiving
MTAs - to preferably not accept.
As does a randomly-generated one...
Mark.
On Fri, Apr 21, 2023 at 5:40 AM Chris Adams wrote:
> Once upon a time, Forrest Christian (List Account)
> 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
> >
On 21/04/2023 15:37, Chris Adams wrote:
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)
-
Once upon a time, Forrest Christian (List Account) 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
> On Apr 21, 2023, at 11:38 AM, Forrest Christian (List Account)
> wrote:
> What's the current thinking around reverse DNS on IPs used by typical
> residential/ small business customers?
> I'm not talking about reverse dns for infrastructure/router IPs here, as I
> still feel those need to
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.
Way way back in the day I used to generate "filler" reverse dns for all of
these ranges .. that is,
15 matches
Mail list logo
