"Email not configured properly" with PTR4 issue

[aurelien-c]

Hi all,

We have in the daily logs:

Email not configured properly:
company.space

PTR4 DNS record (PTR) did not match.
    Hostname: 164.172.73.196
    Expected: my.company.space
    Actual: null

(I've slightly edited the values)
This has been there for a long time.

Now, I had a look at the configuration of our server and it indicates

164.172.73.196
Reverse my.company.space.

A call to "dig -x <ip>" shows:

... IN PTR my.company.space.

The troubleshooting section of the docs do not appear to bear fruit about this.
Any clue ?

Thanks in advance,
Aurélien

[aurelien-c]

TTL issue ? I mean, this symptom lasted a very long time (a full year I'd say). Not seen since early June though. Maybe the "odd DNS issue" then. I guess this can be closed.

[james]

Hello @aurelien-c

When I run:

# Ask Cloudflare about the PTR
dig -x 164.172.73.196 +short @1.1.1.1
# Ask Google about the PTR
dig -x 164.172.73.196 +short @8.8.8.8

I get no answer.
This indicated that no PTR record has been set.

From the documentation https://docs.cloudron.io/email/#ptr-record

The PTR record is set by your VPS provider and not by your DNS provider.. For example, if your server was created in Digital Ocean, you must go to Digital Ocean to set the PTR record.

@aurelien-c said in "Email not configured properly" with PTR4 issue:

The troubleshooting section of the docs do not appear to bear fruit about this.

Did you read the docs.cloudron.io/email/#ptr-record or docs.cloudron.io/email/#troubleshooting?
And, did you configure the PTR in your Hoster?

[aurelien-c]

Sorry I did not provide the real IP. The output of your commands is:

(base) aurelien@trantor:~$ dig -x <ip> +short @1.1.1.1
my.company.space.
(base) aurelien@trantor:~$ dig -x <ip> +short @8.8.8.8
my.company.space.

(domain name also altered)

For me it looks good a priori. The PTR appears to be properly configured at the hosting level, yes.

[james]

Hello @aurelien-c
Did this resolve itself or do you need further assistance?

[aurelien-c]

The last occurrence is signalled on the 6/18/2025 ...
Was there an update in cloudron to address this issue ?

[james]

Hello @aurelien-c
Not that I am aware of.
It could be there simply was some DNS related issues with e.g. TTL causing this.
If this now does not arise again, I would attribute it to some odd DNS issue.

[aurelien-c]

TTL issue ? I mean, this symptom lasted a very long time (a full year I'd say). Not seen since early June though. Maybe the "odd DNS issue" then. I guess this can be closed.