By default, our API is accessible on the api.ricardoneud.com domain. However, you can customize this by setting a custom domain, meaning your clients will be able to access our API on a domain that fits your organization.Custom domains can be set by users with admin permissions. Please follow these steps in order to set a custom domain.
Now that you've added the domain, you need to configure DNS at your DNS provider.Configuring DNS happens outside of Ricardoneud.com, at the DNS provider you are using for your domain.There are two parts to this step:
The names of the fields and what to actually enter to configure the record may differ between DNS control panels, but we've covered the most common options here. If you're uncertain, verify with your DNS provider.
The type is the kind of DNS record that you want to create. Here, you need to choose CNAME.
The name or DNS entry is where you enter your subdomain. You might need to enter it in full (e.g. api.example.com) or you might just need to enter the part before your apex domain (e.g. api). If you're not sure which to use, check with your DNS provider.
The target or value or destination is where the subdomain should be pointed. You should enter api.zone-bind.com as the target value.
You might also see a field named TTL, which stands for Time To Live. It's the number of seconds that the DNS record can be cached for. If you're not sure what to set, we suggest select Auto or remain default value.
Here's an example of how a correct configuration looks in a typical DNS control panel:
Field
Value
Type
CNAME
Name
api
Target/Value
api.zone-bind.com
TTL
1 hr
Note: CNAME record cannot co-exist with another record for the same name. If you already have an A record, AAAA record, TXT record, or any other type of record for your chosen subdomain, you would need to remove those first, before adding the CNAME record.
Are you using Cloudflare?
If you are configuring DNS in Cloudflare's control panel, please ensure that Cloudflare's proxying (the orange cloud, also called "Proxy status" in your domain settings) is disabled. This is for two reasons:
This option obfuscates the DNS target for your domain to the public, preventing proper DNS validation checks.
Your custom domain will already benefit from our CDN infrastructure.
Again, please turn off Cloudflare proxying to ensure that your API is served without issues.
The short answer: you might need to wait 10 minutes ~ 48 hours for the DNS changes to take effect before the system can validate your configuration.Remember the TTL (Time To Live) field we mentioned earlier? DNS records are cached for a period of time — which is usually a very good thing for performance reasons, because they typically don't change very often. When they do change, there is a period of time (the TTL value) where DNS cache servers need their cache to expire before they will check for any changes and behave accordingly.In most cases, it's best to allow at least 10 minutes before the automated validation begins. Sometimes it could all update a bit more quickly, or it could take longer. It's rare for this to take longer than 48 hours.Want to check how this process, known as propagation, is progressing? You could use a DNS lookup tool, such as our DNS Checker. Enter your full subdomain, select CNAME from the dropdown list, and press the Search button. DNS cache servers around the world will respond to let you know what their cached result is. You'll want to periodically check these results until the vast majority respond with api.zone-bind.com.Once your DNS is configured and propagated, the domain will automatically progress through the following stages in your dashboard:
Stage
Description
Duration
DNS Validation
Verifying your CNAME record is configured
2-5 minutes
SSL Provisioning
Requesting SSL certificate from Let's Encrypt
5-10 minutes
SSL Verification
Verifying certificate installation and activation
3-5 minutes
Completed
Domain is active and ready for production
Instant
Coming Soon: Additional SSL certificate providers including Google Trust Services and ZeroSSL will be available for enhanced reliability and redundancy.
The entire process is fully automated. Once DNS validation succeeds, SSL provisioning and verification are handled automatically without any manual intervention required.
SSL certificates are automatically requested and issued via trusted certificate authorities. Currently, we use Let's Encrypt, with Google Trust Services and ZeroSSL coming soon. Verification and renewal are fully automated; no manual intervention is required.
Multiple Certificate Authorities: Certificates are currently issued via Let's Encrypt, with additional providers (Google Trust Services, ZeroSSL) coming soon for enhanced reliability
Automatic Provisioning: Certificates are issued within 5-10 minutes after DNS validation
Automatic Verification: SSL status is checked and verified (3-5 minutes)
Automatic Renewal: Certificates are renewed before expiration (typically 30 days before)
Zero Configuration: No manual certificate management required
Processing Times: The system uses deliberate timing intervals to ensure stability and prevent race conditions:
DNS Validation: 2-5 minutes
SSL Provisioning: 5-10 minutes
SSL Verification: 3-5 minutes
These intervals are designed to prevent duplicate requests and ensure reliable certificate issuance.
Note: Deleting a custom domain will immediately stop routing traffic through that specific domain. However, the API remains fully accessible via api.ricardoneud.com and any other configured custom domains. Ensure you have updated client applications using the deleted domain before removal.
Q: How long does the entire setup take? A: Once DNS is propagated (10 minutes to 48 hours), the automated setup takes approximately 10-20 minutes total (2-5 min DNS validation + 5-10 min SSL provisioning + 3-5 min SSL verification).Q: Which certificate authority is used? A: Currently, SSL certificates are issued via Let's Encrypt. Additional providers including Google Trust Services and ZeroSSL are coming soon, which will be automatically selected for optimal reliability and performance.Q: Can I use a root domain (e.g., example.com) instead of a subdomain? A: We recommend using a subdomain (e.g., api.example.com) as CNAME records work more reliably with subdomains. Root domains can have DNS limitations.Q: What happens if my SSL certificate expires? A: Renewal is fully automatic and happens 20 days before expiration, ensuring continuous HTTPS availability with zero downtime.Q: Can I use multiple custom domains? A: Yes, you can add multiple custom domains to your account. Each will have its own SSL certificate and routing configuration. All domains work simultaneously alongside api.ricardoneud.com.Q: Do I need to configure anything after adding the domain? A: No. Once DNS is configured and the domain is added, everything else is automatic including SSL provisioning, verification, and renewal.Q: What if DNS validation fails? A: Check that your CNAME record is correctly configured and pointing to api.zone-bind.com. Use a DNS lookup tool like WhatsMyDNS to verify propagation.Q: Is there any downtime when switching to a custom domain? A: No. Your API remains accessible on both api.ricardoneud.com and your custom domain. The default domain always remains available regardless of custom domain configuration.Q: Can I use both the default domain and custom domain simultaneously? A: Yes. Both api.ricardoneud.com and your custom domain(s) work simultaneously. You can use whichever endpoint suits your needs.Q: What happens if I delete my custom domain? A: Deleting a custom domain only removes that specific domain. Your API continues to work normally on api.ricardoneud.com and any other custom domains you have configured.
