<![CDATA[Ipv6 changed, issues I don't understand.]]>I changed my router (16/5) (previous one is old, and recently published it has multiple vulnerabilities).
Fine, new router is up and running but self hosted cloudron server has a different ipv6. Gmail was refusing to accept my outbound email.
I really don't know enough to make the new router give the same ipv6. So just logged a ticket for my ISP to update the PTR record.

Cloudron server detects my public ipv6 as 2406:1e00:9b10:1038:9e5c:8eff:fe76:b135
This is what I asked the ISP to set the PTR too. (16/5)
18/5 ISP confirms changes are made
When I checked the AAAA record (19/5) with mxtoolbox it was wrong. 2406:1e00:9b10:10:9e5c:8eff:fe76:b135, it appears to be wrong at digital ocean (automatically updated).

I have manually corrected the data. Also the mail servers PTR self-check is happy again. But I'm still getting...

Failure Reason: Error: 550 5.7.25 [2406:1e00:b910:1038:9e5c:8eff:fe76:b135] The IP address sending this 5.7.25 message does not have a PTR record setup, or the corresponding 5.7.25 forward DNS entry does not match the sending IP

Should I just wait longer?
EDIT: I Just found a typo 9b10 is b910. Hopefully once that goes through it starts working again.
Edit2: Yep its works fine now.

]]>https://forum.cloudron.io/topic/13802/ipv6-changed-issues-i-don-t-understand.RSS for NodeSat, 18 Jul 2026 23:38:08 GMTSun, 18 May 2025 23:20:18 GMT60<![CDATA[Reply to Ipv6 changed, issues I don't understand. on Mon, 19 May 2025 12:26:58 GMT]]>@BrutalBirdie think you missed

Edit2: Yep its works fine now.

😉

]]>https://forum.cloudron.io/post/107358https://forum.cloudron.io/post/107358Mon, 19 May 2025 12:26:58 GMT<![CDATA[Reply to Ipv6 changed, issues I don't understand. on Mon, 19 May 2025 08:34:35 GMT]]>It could be that the TTL of the PTR record was set really high by your ISP 24 to 48 hours.
So it might be that simply waiting will solve this 🤔

]]>https://forum.cloudron.io/post/107347https://forum.cloudron.io/post/107347Mon, 19 May 2025 08:34:35 GMT