Cloudron Forum

Since porkbun returns an 400 error, I might guess something is wrong with the API call we do. Sadly https://porkbun.com/api/json/v3/documentation is not very detailed here, nor is the error message itself.

Possibly the API requires something else for the naked domain, since the subdomains work apparently fine then. But also I can't find anything mentioned in the docs 😕

Can you check if this might be a record conflict error which just reports as 400? Like do A records for that already exist?

Porkbun issue is fixed in 8.1

The porkbun issue is fixed in 8.1

The issue here was server DNS related . The upgrade to Cloudron 8 left the system in a broken state where DNS was not working. Fixing up /etc/systemd/resolved.conf to have DNS servers resolved the problem.

@LoudLemur (Going by the topic subject), if the error is related to PTR record, then the solution is not correct.

The PTR record is set by your VPS provider and not by your DNS provider

PTR record goes by many names - Reverse DNS, rDNS, PTR. Unlike "forward" DNS which looks up something based on the domain name, a "reverse" DNS looks up based on the IP address. And who owns the IP address? The VPS provider. So, you have to change it there.

This means that to fix PTR record issue, you have to fix this in SSDnodes and not in Porkbun or whatever name server you have. If SSDnodes, does not let you set PTR record, you have to ask them by raising a support ticket.

More information at https://docs.cloudron.io/email/#ptr-record

@ByMynix if you want to stick with Porkbun please email them and link https://forum.cloudron.io/post/64902 as the post reproducing the issue. You can also cc support@cloudron.io and we are happy to respond.

@scooke yes, it won't remove your existing records and won't touch things outside scope of Cloudron (which is basically app records and email records).