Hello,
Is there any update on this case? I cannot create new virtual servers on my virtualmin and thus I am currently losing customers and revenue.
Why not remove cloudflare and go back a standard dns setup until someone works out whats wrong, then reinstate cloudflare, that way you wont loose revenue
Does your Cloudflare configured to use âEmail and API keyâ or âAPI tokenâ?
I have tried both methods with all the required API permissions
Iâm really baffled about whatâs going wrong on your side. I ran more in-depth tests, and it worked just fine in all of them!
Could you send a support message to @staff, include a link to this topic, and share your server login credentials? One of our team members will log in and take a closer look to see whatâs going on.
So, after debugging it for hours I set this value to automatic and it worked. (the custom value was the same)
I really donât know why and how.
We are very glad to hear that you managed to solve this; however, this option shouldnât matter at all.
@Jamie, do you have any idea what might be happening here?
Assuming you used copy and paste the value may not be the same
One thing to try is applying this patch, and then see if you get any more details in the error message when domain creation fails : Show error message properly · virtualmin/virtualmin-gpl@31f1cc7 · GitHub
@Jamie did we ever get any clarity on this?
- Fresh system with no virtual servers
- Existing domains already on cloudflare as the registrar with no existing dns records
- Server template updated to Cloudflare for dns
Same error
Adding new DNS zone hosted by Cloudflare DNS ..
.. failed to generate records :
I can add the local system back as a remote server, and switch back to local and get records to generate locally. I am looking to exclusively use cloudflare as a registrar and nameserver for all records.
I tried different combinations of permissions, and also attempted to use email+global api key.
Try applying this patch and give it another shot. It should display a clearer error message.
webmin patch https://github.com/virtualmin/virtualmin-gpl/commit/31f1cc7
Ok, thatâs provides some context. It looks like the core of the problem is that the system isnât adapting its default dns template stack to push into cloudflare. It canât seem to figure out what it should be using. Do we need to populate a different default template when using cloud dns? I dndât see that step outlined and I would think it reasonable to assume it would create basic records it needs.
.. failed to generate records : No NS records found in template!
More specifically itâs tripping over ns records which it shouldnât need as those are defined in cloudflare already. What should the workflow look like and I can try to test it directly.
@Jamie Thoughts?
@Ilia I was able to get past the problem by adding the Cloudflare nameservers to the template as additional manually configured nameservers. Editing the template and added these, which all of my servers currently use, but may not be consistent globally. Editing an existing entry that was failing to turn back on the DNS Options, and the records were all populated and pushed properly.
Cloudflare has lots of nameservers, and my suspicion is everyone is usually a different set. If it is allocated per account, that would make the fix as simple as an additional step. If not it may require some type of api query to check the nameservers for an existing domain dynamically.
Blockquote
[Additional manually configured nameservers]
lennon.ns.cloudflare.com
melina.ns.cloudflare.com
Try applying this patch, which removes that nameserver check which is irrelevant when using Cloudflare : No need for nameservers if we're using a DNS cloud · virtualmin/virtualmin-gpl@9873dfc · GitHub
Patch tested and working.
Excellent! This will go into the next release.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.