[TriLUG] recent "Poor Reputation Sender" bounces

[Matt Flyer via TriLUG]

On Tue, 2019-07-09 at 10:08 +0000, Joseph Mack NA3T via TriLUG wrote:
> I notice that pilot is nat'ed.
> 
> pilot: $ ifconfig | grep "inet addr"
>      inet addr:192.168.122.3
> 
> I was sending to a CS person at a university. I don't expect them to
> get a 
> different e-mail address because pilot's reverse DNS doesn't match
> its forward 
> DNS.
> 
> I know that pilot is hosted at a data center somewhere in Raleigh and
> we only 
> have the machine by the good graces of the data service. Since pilot
> is NAT'ed, 
> is it true that we're never going to have our own reverse DNS?

Two comments: One, the 192.168.122.3 is an RFC1918 address, which means
it is not publicly routable (or shouldn't be as I've caught the company
formerly known as Slime Warner sending packets with these addresses to
my modem's public IP).  It is only usable on a private network.

Doing a quick look around on Pilot, the eth0 interface is configured by
DHCP and it gets assigned a default gateway of wm-net, which resolves
to 192.168.122.1. So yes, it is obviously NAT'ted.  However, as it can
accept inbound connections it is likely a 1:1 dereferencing, which
leads to the second comment.

Two, I would expect that the hosting provider has an option in the DNS
configuration to assign the reverse lookup record.  It should be
somewhere in or around the section where you assign the forward A
record and other custom entries.