Uhm, no. For example: If you would ask 8.8.4.4 the in-addr.arpa for "your" rented OVH ip resource, then 8.8.4.4 would go and ask OVH for the answer. And no, Spamhaus does not "red flag" any ipv4/6 resource for lack of a reverse name. So no mystery for me here... OVH is known for being less than responsive to abuse complaints. Also, judging from your post, OVH is also economic with the truth? Your reverse setting took a day or two because OVH did not update your request and as far as Spamhaus goes: OVH had to promise that their abuse has stopped, to have their resources removed. No IP becomes listed simply because it has no reverse name setup. In fact, there is no technical requirement to even have a reverse name setup. But, for some types of spam, 99.9% of the time, that specific type of abuse resource has no reverse, which is why over 50% (by volume of servers) of mail servers do not talk to you without your ipv having a reverse name... Then again, by volume of email (not by volume of servers), over 87% of email boxes will accept email from you, with no reverse name configured. (The reason for this is partly the large dominance of Google & Microsoft - One of which accepts email from ipv with no reverse and the other being unpredictable as it does anything at any time) Anyway, as usual, ymmv. hth Andre On Wed, 27 Feb 2019 10:38:09 -0500 Marc Lijour via talk <talk@gtalug.org> wrote:
Happy to report that OVH got it fixed for me. They replied to the support ticket within 24 hours. After two interactions we were done. They said it took some time for the reverse DNS to replicate (for the reverse record I did setup days earlier). Whether it was just that delay or they did something in the backend, the dig -x command now reports the correct information. No Spamhaus red flag since then. Happy end.
On Fri, Feb 22, 2019, 20:20 D. Hugh Redelmeier via talk, <talk@gtalug.org> wrote:
| From: Val Kulkov via talk <talk@gtalug.org>
| Do you have a permanent static IP address? If not, you may occasionally be | picking up a "dirty" IP address.
It's clear (now) that Marc has a static IP address.
It really isn't worth trying to use a dynamic IP address for mail. But I did it.
I used to use a Rogers connection for a secondary email server. I could use the domain name they gave me, and the reverse domain would agree (but was out of my control). The IP address would change at the rate of roughly once a year. That would cause a bit of disruption because the transition was carelessly managed by Rogers.
I still use Rogers for bulk IP traffic but maybe not for long: they are kind of doubling the cost for my "bundle" and I find that annoying.
| From: Don Tai via talk <talk@gtalug.org>
| You're on a shared host with any number of other web sites and owners. When | one goes rogue and launches bots at the world the IP is logged and is used | to ban all the sites on that IP, which might include your own. Bots | reappear on a regular basis, using the same IP, so bans, in general, are | for life.
It's clear (now) that Marc has a dedicated IP address.
It depends on what you mean by "shared host". Normally that means several web sites sharing one IP address. I don't think that you can do that with SMTP.
You could mean several people sharing one box, but with each having their own IP address. That should work for email.
I, for example, rent a couple of OpenVZ instances in the cloud, each with their own IP address. Each physical box is shared by untold numbers of OpenVZ instances. I'm allowed to set the reverse domain records for them. (Control of one's own forward domain is not a problem.) They each cost less than $20 per year. I don't run mail servers on them but I'm sure that I could. They both run CentOS 7. --- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk