Some DNS records are missing or incorrect for domain xxx.yyy.com (category mail)

[agichim]

My YunoHost server

Hardware: VPS bought online - netcup.eu
YunoHost version: 4.1.7.4 (stable)
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen |
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Hello!

I have installed Yunohost on a VPS from netcup and pointed it to a subdomain from Namecheap.
When I updated the DNS on Namecheap most got configured immediately, but a few DNSs throw this specific error (below the error is the full paste yunohost log)

Current value: "\"v=spf1 a mx -all\""
Expected value: "v=spf1 a mx -all"

When I go into my DNS on Namecheap the record shows the “expected value”, the correct one. This happens with a few records. See the link below. The different between current and expected value is the extra "\ at the beginning and the extra " at the end.

I don’t know what I have to do make Yunohost read the correct value.

https://paste.yunohost.org/raw/exelulobet

See screenshot for Namecheap records. The value is the Expected value by Yunohost, but when I run the diagnosis on Yunohost it reads a different value.

Another question is whether pointing Yunohost to a subdomain it is needed to be configured differently than if pointing to a main domain. I’m not talking about installing and pointing an application to a subdomain, but pointing Yunohost itself. Are the settings different if pointing to a subdomain?

Thank you.

[Acidope]

Hi Agichim,

Not sure about that, but I think having a subdomain as “main” domain is not to recommend. It depend on what u gonna do with ur YNH.

otherwise for your line, my record appear like that :
"v=spf1 a mx ip4:XX.XX.XX.XX ip6:XXXX:XXXX:XXXX:XXXX -all"

But this line is important if you use yunohost as mail server.

My knowledge is quite limited, I hope not to tell you nonsense.

[ljf]

@agichim

“"v=spf1 a mx -all"”

This mean you probably write double quotes inside the namecheap interface. You should not write the double quotes yourself, if Namecheap give you something like a wizzard to configure your DNS SPF entry. So you just need to write in namecheap field:

v=spf1 a mx -all

and not

"v=spf1 a mx -all"

[agichim]

@ljf I have actually removed the quotations once, but at that point I was so impatient that I didn’t give enough time for the DNS changes to propagate. That was so plain and easy, I was just too tired trying to understand what was wrong!

Thanks!