Porkbun is now on the list for DNS API in Cloudron 7.4
-
I've always used Wildcard, partly because the domain providers I use aren't on the Cloudron list. It seems like a good idea, I guess, right? You punch in your API key and voila, all your Cloudron details are entered.
BUT
What happens to the current settings? For example, I use the Cloudron email for the main domain, but MXRoute for all the others. I use some root domains elsewhere, but use blog.example.com on Cloudron. And vice versa. What will happen in I switch to an API? When Cloudron automatically sets my DNS up will it delete all those other records. I'm not too keen to go trawling through my docs to find my SPF and DKIM records, for example, to re-enter everything!
A life lived in fear is a life half-lived
-
I've always used Wildcard, partly because the domain providers I use aren't on the Cloudron list. It seems like a good idea, I guess, right? You punch in your API key and voila, all your Cloudron details are entered.
BUT
What happens to the current settings? For example, I use the Cloudron email for the main domain, but MXRoute for all the others. I use some root domains elsewhere, but use blog.example.com on Cloudron. And vice versa. What will happen in I switch to an API? When Cloudron automatically sets my DNS up will it delete all those other records. I'm not too keen to go trawling through my docs to find my SPF and DKIM records, for example, to re-enter everything!
@scooke Cloudron does not delete any existing records. It doesn't "own" the DNS as such.
All it's going to do is to add records when you install an app, delete them when you uninstall it. Email records are also not touched. It will only add your Cloudron to the SPF record (it will edit any existing record). Finally, if you use foo.example.com externally and you try to install an app at foo.example.com, it will warn you that there is already a DNS record in that location and seek your confirmation to go ahead and overwrite it.
-
I've always used Wildcard, partly because the domain providers I use aren't on the Cloudron list. It seems like a good idea, I guess, right? You punch in your API key and voila, all your Cloudron details are entered.
BUT
What happens to the current settings? For example, I use the Cloudron email for the main domain, but MXRoute for all the others. I use some root domains elsewhere, but use blog.example.com on Cloudron. And vice versa. What will happen in I switch to an API? When Cloudron automatically sets my DNS up will it delete all those other records. I'm not too keen to go trawling through my docs to find my SPF and DKIM records, for example, to re-enter everything!
@scooke said in Porkbun is now on the list for DNS API in Cloudron 7.4:
I've always used Wildcard, partly because the domain providers I use aren't on the Cloudron list
Out of curiosity, what other providers do you use
? -
@scooke said in Porkbun is now on the list for DNS API in Cloudron 7.4:
I've always used Wildcard, partly because the domain providers I use aren't on the Cloudron list
Out of curiosity, what other providers do you use
?@girish Namesilo, Dynadot, Porkbun, and 2 on namecheap (for various reasons I've been moving away from namecheap...for the rather silly reason that they call DNS "Advanced DNS". There were maybe a few other glitches, but I just haven't like that what other registrars offer as just normal, day-to-day DNS settings is all fancied-up as "Advanced". They've also pushed alot of upselling before... so I've been moving away. I admit to buying domains during their sales, but then I move them to one of the other 3 for the renewal price.
-
I contacted Porkbun to inquire about their DNS stats since they're not listed on DNSPerf.com and it turns out they're using Cloudflare for their DNS services.
Hello, Thanks for reaching out. Our nameservers operate on Cloudflare's DNS platform, so performance should be identical to Cloudflare, and that could be why our nameservers are not evaluated by them separately. Hope this helps. Please let us know if you have any questions or if there's anything else we can help with. Best, Andy Support Engineer -
@scooke Cloudron does not delete any existing records. It doesn't "own" the DNS as such.
All it's going to do is to add records when you install an app, delete them when you uninstall it. Email records are also not touched. It will only add your Cloudron to the SPF record (it will edit any existing record). Finally, if you use foo.example.com externally and you try to install an app at foo.example.com, it will warn you that there is already a DNS record in that location and seek your confirmation to go ahead and overwrite it.
@girish said in Porkbun is now on the list for DNS API in Cloudron 7.4:
add records when you install an app, delete them when you uninstall it
Do we still need to use the * in the DNS settings for domains using a API?
A life lived in fear is a life half-lived
-
@girish said in Porkbun is now on the list for DNS API in Cloudron 7.4:
add records when you install an app, delete them when you uninstall it
Do we still need to use the * in the DNS settings for domains using a API?
@scooke said in Porkbun is now on the list for DNS API in Cloudron 7.4:
Do we still need to use the * in the DNS settings for domains using a API?
Nope, not needed when using the Programmatic DNS.
-
@scooke said in Porkbun is now on the list for DNS API in Cloudron 7.4:
Do we still need to use the * in the DNS settings for domains using a API?
Nope, not needed when using the Programmatic DNS.
@girish So, if I change an existing domain's setting to Porkbun, the API will check and see that at least there is an A record for the domain, see that there are MX records, and CNAME records, etc., but not change anything because the A Record is already there... correct? Nothing will be changed?
And if I remove the domain, the API will simply remove just the A Record, correct, leaving everything else untouched?
A life lived in fear is a life half-lived
-
@girish So, if I change an existing domain's setting to Porkbun, the API will check and see that at least there is an A record for the domain, see that there are MX records, and CNAME records, etc., but not change anything because the A Record is already there... correct? Nothing will be changed?
And if I remove the domain, the API will simply remove just the A Record, correct, leaving everything else untouched?
@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).
