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


Skip to content
  • PTR record reports being set wrong

    Solved Support
    20
    1 Votes
    20 Posts
    418 Views
    A

    it just went away, i think the router had a DNS cache thats flushed now. It's no longer being set as the DNS server via DHCP, so I think its resolved.

  • PTR record on AWS EC2

    Solved Support
    4
    1 Votes
    4 Posts
    181 Views
    G

    @girish Ha ok, makes sense, will try setting up the relay and update the thread. Thx!

  • 1 Votes
    2 Posts
    89 Views
    girishG

    @p44 thanks, fixed.

  • PTR problem between Linode & Mastadon

    Solved Support
    31
    0 Votes
    31 Posts
    503 Views
    C

    @DeBossNow

    I am glad you got it resolved, but just to clarify:

    The MX record is for incoming email. It needs to be set to any domain name that resolves to your server, i.e. has a valid A record. If both my.currentdoain.de and currentdomain.de resolve then you can use either for incoming mail. The mismatch was not with the MX record but between the mailserver domain set in Cloudron and the PTR record of the server. At no point did I or anyone else tell you to change the MX record, and no, the PTR error had nothing to with the MX record. I can therefore only assume that you interpreted MX as being something it is not.

    For outgoing mail you need a valid PTR record that matches the mailserver domain. You also need a valid SPF record and a valid DKIM entry.

    Because you set up Cloudron via the Linode app you have presumably told Cloudron to use Linode DNS, which is why it is updating / overriding certain settings. If you do not want it to do that you need to set DNS to manual for the resepctive domain(s).

    The bottom line is: The PTR record and mailserver domain have to match. Where you make the changes depends solely on the domain you want to use for email, i.e. where the entry needed updating to match.

    Btw, I stated every time that you needed to check / update the mail domain in Cloudron, not in the Linode dashboard.

  • 1 Votes
    3 Posts
    132 Views
    girishG

    See this - https://docs.cloudron.io/email/#ptr-record

  • Need help with PTR Reverse Domain setup

    Solved Support
    7
    0 Votes
    7 Posts
    315 Views
    MooCloud_MattM

    @zion
    you have to ask to set it up to the company that rent you the IPv4/v6.

    Most likely they have an option on their control panel to do that.

    If you have ownership of the IP, just do it from Virtualizor, google "Virtualizor ptr" and the first result is https://www.virtualizor.com/docs/admin/configure-reverse-dns/
    --> you can do this only if you bought it and the ip is yours

  • PTR record resolves incorrectly.

    Solved Support
    3
    0 Votes
    3 Posts
    215 Views
    nebulonN

    thanks for sharing the root cause!

  • 0 Votes
    12 Posts
    693 Views
    girishG

    @christiaan On linode, if you are a new account, you can usually open a support ticket and explain your use case of email hosting to them and they usually unblock port 25.

  • PTR record hetzner

    Solved Support
    5
    0 Votes
    5 Posts
    1k Views
    xemdagabettingX

    @jdaviescoates ok, good

  • 0 Votes
    6 Posts
    573 Views
    JOduMonTJ

    @YurkshireLad you should rectify your PTR your email will have a better change of being receive.