PTR problem between Linode & Mastadon
-
I have successfully installed Cloudron after creating a new server volume at Linode. And it installed Mastadon within 5 minutes. Success at last.
Now I see a problem that I first encountered a couple of years ago when setting up the standard Cloudron Email. Emails will work correctly but in the Email configuration window I see this familiar error again.
the following --
Email configuration
The PTR record is set by your VPS provider and not by your DNS provider.
Hostname: xx.xx.xxx.xxx
Record type: PTR
Expected value: my.currentdomain.de
Current value: currentdomain.de**At my Linode dashboard I see that Cloudron has set the
MX Record to be
Mail Server Preference Subdomain
my.currentdomain.de 10But the PTR check expects to see in my Linode configuration a complete my.currentdomain.de as well, instead of simply my
Linode Configuration --
A/AAAA Record
Hostname IP Address
currentdomain.de xx.xx.xxx.xxx
my xx.xx.xxx.xxxI cannot get this record to change to my.currentdomain.de ---- Linode does not allow it to be saved this way. It by default reverts to simply my
I've looked through the forum history and done online searches but I don't find a resolution to making this PTR Error disappear in my Cloudron dashboard. Linode tech support refers back to my Cloudron account to somehow resolve the error. I may have to live with this error as long as I am using Linode but as far as I know the emails work.
Does someone using Linode and Cloudron have a way to resolve this problem in 2023?
Thanks for any relevant helpful answers! -
@DeBossNow have you read this?
PTR aka reverse DNS aka rDNS
-
@jdaviescoates Yes, I have read this. Thank you.
But it resolves to just saving the prefix my even when I enter my.currentdomain.de
It seems that my Cloudron function, the actual value it is checking for, would have to be changed in the script itself to remove the PTR error. It is looking for a literal my.currentdomain.de string and can not resolve simply seeing a my by itself.
-
@DeBossNow
Cloudron can not set a PTR/rDNS record since its on the provider / server side.You can check your PTR record manually with the following command:
dig -x YOUR_SERVER_IP_GOES_HERE +shortYou can also optionally add a DNS Server to check against with e.g.
@1.1.1.1
Example:dig -x YOUR_SERVER_IP_GOES_HERE +short @1.1.1.1If you have in https://my.YOUR.DOMAIN/#/email =>
Mail server location my.YOUR.DOMAINthen thediglookup should return exactly that.
If not, set the value correctly in your provider panel. -
@BrutalBirdie Thank you.
But, as I have written -- I showed and described what I can do on my server side. I KNOW that the PTR is set on my server side.But, as I wrote --- the Linode UI tools for the A/AAAA adminstration will write that value as -- my
NOT my.currentdomain.deAnd this apparently works fine for thousands and thousands of sites set up for hundreds of thousands of Linode users with all kinds of apps.
Only Cloudron, that I have run across, demands to see this record as -- my.currentdomain.de
The setup which it only does once -- in the MX record -- but NOT in the records the Cloudron PTR check is looking for -- in the A/AAAA records.Cloudron PTR check is the anomoly here unless someone has ACTUAL EXPERIENCE WITH LINODE and found a work around.
-
@DeBossNow It seems obvious that the PTR check should recognize that the Linode server environment is Different from, say, Hetzner, etc. and knowing that important fact it will adjust its expectations for that PTR string and give it a green light.
A simple if/or/then check to handle the query back to the Linode environment where Cloudron is installed.
-
I am not really understanding your problem. In Cloudron you can set the mail server location to be whatever you want. It will default to my.domain.xx after installation but you can change it to domain.xx so that it matches the PTR record.
The MX and A/AAA records have nothing to do with this. Cloudron just checks that there is a PTR record that matches the mailserver hostname. Also the server environment is irrelevant.
-
@DeBossNow, where are you configuring your rDNS settings? I don't have that issue. I can set
sub.domain.tldin the Networking tab of the Linode that Cloudron is installed on... -
@ccfu
"Cloudron just checks that there is a PTR record that matches the mailserver hostname. Also the server environment is irrelevant."If this was happening as you say then the Cloudron check would be happy with the MX record. NO Error.
As I showed -- the reason I INCLUDED IT Twice now --
is that the MX record, while set up BY Cloudron when I elected to use the default SMTP server for outgoing mail -- then set by Cloudron as my.currentdomain.de -- does NOT SATISFY the PTR checkObviously, the PTR check keeps referring to the A/AAAA Records. It SCANS NOT the MX record which IS my.currentdomain.de ---
but focuses on looking for another kind of record.I did not install a separate email server app. I am just using the vanilla Cloudron email server setup which GENERATED the MX Record on my Linode server.
i do NOT WANT TO CHANGE anything more.
But the PTR check is reporting that is it finding
my standard DNS reverse currentdomain.de linked to my public IP. And it is demanding that to be happy that it finds a PTR record that literally contains this string --
my.currentdomain.deThis is just plainly NOT HAPPENING as you describe:
"you can change it to domain.xx so that it matches the PTR record."
I WANT THE PTR TO JUST LOOK AT MY MX RECORD AT MY SERVER AND STOP REPORTING AN ERROR.How many times can I repeat this and still confuse you?
IF the PTR Check in Cloudron was simply referring to the MX Record my.currentdomain.de then NO ERROR.
All I can do is REPORT what Cloudron's PTR Check is showing me. ERROR. -
@DeBossNow can you please share your domain name so I can have a look?
-
The MX record has nothing to do with outgoing mail. Cloudron doesn't care what the MX record is and does not even look at it!
Does the PTR record of your server match the mailserver location on the page
/#/email? Is there an A record for this (sub-)domain? If you can answer both these questions with YES, then the checks will pass. -
@colonelpanic Thank you for trying to help.
I REALLY DO KNOW BACKWARDS AND FORWARDS WHAT I CAN SET IN MY LINODES ACCOUNT.
I HAVE SET UP 6 WEBSITES, ALL NODE.JS ETC AT LINODES.
I HAVE MADE MANY MORE VOLUME SETUPS FOR DIFFERENCT SCENARIOS
THERE IS JUST NO WAY THAT USING THE LINODE TOOLS I CAN ADD A SEPARATE DNS ENTRY IN THE A/AAAA Records that assigns my public IP address to an entry that reads the following string --- my.currentdomain.de
If I could literally save that value then, presumably, the Cloudron PTR would be satisfied.LITERALLY the Linode DNS tools, once the main domain name is entered, the Sub domains such as MY or WHATEVER.currentdomain.de will NOT SAVE AS SUCH.
The base domain name is STRIPPED out ... leaving only the PREFIX of the sub domain.
-
@DeBossNow WHY ARE YOU SHOUTING?
The base domain is not stripped out, it is just not showing because it is clear what the domain is. If the domain were being stripped out, nothing would work!
This is NOT the problem. The problem is a mismatch between the mailserver location in Cloudron and your server's PTR record.
Again:
@ccfu said in PTR problem between Linode & Mastadon:
Does the PTR record of your server match the mailserver location on the page /#/email? Is there an A record for this (sub-)domain? If you can answer both these questions with YES, then the checks will pass.
-
@DeBossNow
If I had an account at Hetzner, for instance, I could do what I am used to doing for years and years --currentdomain.de -- IP xx.xxx.xxx.xx
my.currentdomain.de -- IP xx.xxx.xxx.xxbut when I write and save at Linodes the subdomain prefix my. or any other prefix mail. or whoopee. etc is STRIPPED from its base domain and gets saved, no matter what as --
my -- IP xx.xxx.xxx.xx
-
@DeBossNow It is just an interface issue. Linode appears to not show the domain part, whereas other providers do. I use two different DNS providers - one shows the domain, the other one does not. The DNS zone is the domain part so EVERYTHING that is saved is .domain.xx
-
@ccfu I know that it is not really stripped out.
I know that.
What I am saying is that the Cloudron PTR checking script does NOT include this value.
It is reporting back that it wants to find the literal string "my.currentdomain" but all it finds is "currentdomain.de" and that it is expecting to find "my.currentdomain.de".I am incredibly frustrated by now. I cannot report it more clearly than I have. About 3 years ago I read about the SAME PROBLEM on this PTR check with Linode. I never saw a solution. Emails worked. Move on. Ignore it seemed to be the consensus.
I was hoping in 2023 this would be resolved.
-
@DeBossNow please be more respectful with everyone in this forum.
Everyone here is helping out of there good heart and using their free time to respond to you.
Do not take this for granted!Since you ignored my request to share your domain so I can not confirm your DNS settings.
I have set up 100x more Cloudron servers on almost any provider out there and can not relate to your issue.
Right now for me it simply reads like you have no clue where to set the PTR record since it's not the same interface as the normal A/AAAA DNS settings. (My view, must not be true!)So once again, can you share your domain so I can have a look?
And again, be more respectful with the people here. Last warning.
No matter your frustration level you are writing with real humans here. -
@ccfu l understand the interface problem.
I did not start in this stuff a week ago.I am telling you that the PTR check is what does not understand, so to speak, the "Interface problem".
I do not have access to the Cloudron PTR check script to modify it for what it finds when it checks the server configuration at linodes.
It is an inteface mismatch not with ME but with the internals of the script. It does not find the literal string "my.currentdomain.de" -- it obviously ONLY finds "currentdomain.de". There is an adjacent record at Linode that should contain the value "my.currentdomain.de" just as the MX record contains.
But I cannot edit, I cannot add that DNS reverse lookup value as "my.currentdomain.de". And, obviously Linode does not read out that full prefix with base domain name to the Cloudron PTR script.
I thought this would be simple. I am done. I thank you for all your help, everyone.
