Netcup Error - TXT and MX record
See original GitHub issueI tried the pullrequest for “Netcup” and it works most of the way but it giving some errors at the end. The examples are these once:
ERROR - create für Eintrag MX/nitter.maindomain.tld fehlgeschlagen: MX record destination is incorrect. An example of a correct entry: mail.nitter. (4013)
ERROR - create für Eintrag TXT/_dmarc.nitter.maindomain.tld fehlgeschlagen: Please put quotation marks in front of a backspash. The name server automatically sets quotation marks at the beginning and end. (4013)
Can i somehow help so solve the problem? I use lexicon within yunohost and the full errorlog is here.
Thanks you a lot!
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Internal Error with netcup and DNS Challenge #1706 - GitHub
I want to access my internal password management (vaultwarden) with NPM. Therefore I created in Netcup an A-Record with Destination my internal ...
Read more >DKIM not working - Dynadot
I set up almost all records correctly (two MX, a CNAME for email subdomain and the SPF TXT record on the main domain)....
Read more >Error with DNS and Netcup - Support - YunoHost Forum
If i start the autoconfig it gives some errors. MX record destination is incorrect. An example of a correct entry: mail.bibliogram. (4013).
Read more >Webhosting 1000 SE iv - Product details - Netcup
DNSSEC on request: Yes, if supported for TLD. DNS records: A, AAAA, MX, CNAME. TXT, SRV, NS ... Access to log files: Yes....
Read more >TXT Entry DNS für vServer - netcup Forum
Danach muss man natürlich noch die entsprechenden MX Records eintragen, ... Ich stehe genau vor dem selben Problem: ich habe den TXT Record ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
From what I see in the logs, it seems that the MX records should be inserted with a trailing dot in the content, and the TXT record content should be enclosed with quotes.
It seems also that the values of the records are passed verbatim from the command line flag
--content
to Netcup API. Could you retry the calls with content of kindmail.domain.tld.
for the MX records and'"My content"'
for the TXT records ?@adferrand Thanks for the clarification. @alexAubin So there is nothing we can do right?