Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Ipv6 changed, issues I don't understand.

Ipv6 changed, issues I don't understand.

Scheduled Pinned Locked Moved Solved Support
networkingipv6
3 Posts 3 Posters 63 Views 3 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      A Offline
      AartJansen
      wrote last edited by joseph
      #1

      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.

      BrutalBirdieB 1 Reply Last reply
      2
      • A AartJansen

        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.

        BrutalBirdieB Offline
        BrutalBirdieB Offline
        BrutalBirdie
        Partner
        wrote last edited by
        #2

        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 🤔

        Like my work? Consider donating a drink. Cheers!

        jdaviescoatesJ 1 Reply Last reply
        1
        • BrutalBirdieB BrutalBirdie

          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 🤔

          jdaviescoatesJ Offline
          jdaviescoatesJ Offline
          jdaviescoates
          wrote last edited by
          #3

          @BrutalBirdie think you missed

          Edit2: Yep its works fine now.

          😉

          I use Cloudron with Gandi & Hetzner

          1 Reply Last reply
          1
          • J joseph marked this topic as a question
          • J joseph has marked this topic as solved
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Bookmarks
            • Search