Updated October 30, 2026. Custom subscription domains now use Cloudflare for SaaS. Set the CNAME target to nodebuf.com. If your domain currently points to ingress.nodebuf.com, migrate the existing record with the steps below.
Keep a working main-site URL first
Before changing DNS, copy a complete nodebuf.com URL from Subscriptions, Files, or Short links. Keep the path and every access parameter.
There may be a short interruption between the DNS change and certificate deployment. The main-site URL is your fallback. Do not delete and recreate an existing domain. Update its DNS, then verify the retained record. Your subscriptions, files, IDs, and access keys remain in place.
What changed
| Setting | Current value |
|---|---|
| Your CNAME target | nodebuf.com |
| Proxy status of your customer-domain CNAME | Orange cloud / Proxied is recommended on Cloudflare; DNS only also works |
| Ownership proof | The _nodebuf TXT displayed in your account |
| Additional Cloudflare proof | Add any extra TXT records shown on the page |
| HTTPS | Issued, deployed, and renewed by Cloudflare |
| Existing subscription and file data | Retained |
If your domain is also on Cloudflare, orange cloud / Proxied is recommended through O2O. Your zone and Nodebuf must be in different Cloudflare accounts; same-account zones can use DNS-only mode. Other DNS providers can keep ordinary CNAME routing. Previous gray-cloud instructions reflected the earlier application limitation; gray cloud remains supported, so working records do not need to be recreated. Nodebuf manages the main-site zone. You do not need to share a Cloudflare API token or call the API yourself. Proxying can reduce direct origin exposure, but it cannot guarantee access from every network or prevent every domain restriction.
1. Open the retained domain
Visit Custom domains, under User space → Connections and files.
For an existing domain, select its current record. For a new domain, use Add domain and enter a hostname such as sub.example.com, without a scheme, port, or path. Use your own account's DNS values; the names below are examples.
2. Update DNS
A subdomain
For sub.example.com, configure:
| Type | Full name | Value | Proxy |
|---|---|---|---|
| CNAME | sub.example.com |
nodebuf.com |
Orange cloud recommended on Cloudflare; DNS only also supported |
| TXT | _nodebuf.sub.example.com |
Copy the full value from your domain page | DNS only |
If the provider appends example.com automatically, the record names are usually sub and _nodebuf.sub. Check the preview: sub.example.com.example.com is wrong. The CNAME value contains no https:// or trailing path. Remove conflicting records at the same hostname instead of leaving A/AAAA records pointing elsewhere. Do not replace the CNAME with a Cloudflare IP copied from a lookup.
If the retained record points to ingress.nodebuf.com, change that CNAME target. Keep an existing correct _nodebuf TXT. Copy the entire displayed value; quotation-mark handling depends on your DNS provider.
A root domain
The root domain example.com is supported when your DNS provider offers CNAME flattening, ALIAS, or an equivalent feature. In a Cloudflare zone:
| Type | Name | Full name | Value |
|---|---|---|---|
| CNAME | @ |
example.com |
nodebuf.com, orange cloud recommended for O2O; DNS only also supported |
| TXT | _nodebuf |
_nodebuf.example.com |
Your displayed ownership value |
A flattened root may return A/AAAA rather than a visible CNAME. Nodebuf checks the ownership TXT and resolved addresses. If flattening is unavailable, use a subdomain; an arbitrary A record is not an equivalent setup. Changing a root-domain record may also affect a website already using that hostname. A dedicated subscription subdomain avoids that conflict. See Cloudflare's flattening documentation.
3. Verify DNS and HTTPS
Return to the retained domain and select Verify DNS and HTTPS, or Verify again. Nodebuf checks your current ownership TXT, the CNAME or flattened addresses, Cloudflare hostname activation, and certificate deployment.
If extra TXT records appear, such as _cf-custom-hostname or _acme-challenge, add the exact names and values shown for your domain. Do not use values from another person's screenshot. Allow DNS caches to update, then verify again.
Both the Cloudflare hostname and SSL states must be active, and current DNS must pass. A successful Add action or an active hostname alone does not mean HTTPS is ready. While issuance is pending, wait and verify again instead of deleting and recreating the record.
For old moved, deleted, or timed-out Cloudflare records, verification can restart validation after your current DNS passes. If the page asks an administrator to investigate, send the hostname and stable error code through private messages. Keep access keys out of public discussions.
4. Copy the complete subscription URL
When the page says the domain is usable, open your subscription, file, or short-link page, select the domain, and copy the complete URL. A bare address such as https://sub.example.com is not a subscription.
If replacing the host manually, preserve the path, query parameters, and keys. Refresh the subscription in your client after migration. Main-site URLs continue to work; nodes, templates, and file contents do not need to change.
Allowed access
Custom domains serve their owner's dynamic subscriptions, static file downloads, repository forwarding links, and site short links. Existing supported server-panel subscription routes keep their resource checks.
They do not mirror the website. Visiting a homepage, tool, login page, or admin page through a custom domain shows a restricted-access notice. That is expected; manage your account at nodebuf.com. Binding a domain does not remove file permissions, subscription keys, or device restrictions.
Orange-cloud routing and subscription clients
We verify ownership TXT, all public DNS answers, Cloudflare hostname and SSL states, and a short-lived signed HTTPS response proving this hostname reaches Nodebuf. Matching a Cloudflare IP alone never proves correct routing. Keep /.well-known/nodebuf-domain-route/ reachable.
On subscription and verification paths, avoid interactive challenges, Cloudflare Access login, redirects to another site, and Cache Everything rules. Subscription clients cannot complete browser login or challenges; forced caching can serve outdated content. Keep certificate verification enabled. If HTTPS routing verification fails, check the CNAME and these rules, then verify again. Owner and resource restrictions stay unchanged.
See Cloudflare O2O documentation.
Troubleshooting
CNAME mismatch
Check the target is nodebuf.com, rather than the old ingress address. Check the CNAME target, conflicting A/AAAA records, duplicate domain suffixes, and DNS caches. Orange cloud conceals the CNAME and may use different Cloudflare IPs from the main site; that alone is not a failure. Root domains need flattening support.
TXT missing or incorrect
Use the value on the current account's domain page. Check all subdomain levels in the name. Retain the record throughout verification. Do not use a previous screenshot or another account's proof.
Hostname active, SSL pending
The two states are independent. Add any displayed validation TXT, wait, and verify again. A successful browser TLS connection alone does not prove the custom certificate finished provisioning. Persistent failures may also involve restrictive CAA records; provide the error code to the administrator.
Deletion awaiting confirmation
Nodebuf disables access first, requests remote deletion, and confirms the Cloudflare object no longer exists. A network failure leaves the record and its slot reserved. Retry removal later instead of adding the same hostname again. Removing a domain does not delete subscriptions, files, or their main-site URLs.
Capacity reached
Each account may retain 10 domains. The application has a global limit of 100, including pending and unresolved-deletion reservations. Administrators can inspect, validate, suspend, and remove records under Files and links → Custom domain management. Users cannot manage someone else's domains.
I have not migrated yet
Retained DNS-only domains have migration compatibility. This update does not change customer DNS or delete old records. Migrate using the new page when practical, keep a main-site fallback during the change, and wait for both Cloudflare states before updating clients.
Final checklist
- CNAME points to
nodebuf.com; orange cloud is recommended on Cloudflare and DNS only remains supported. - Your ownership TXT and any additional displayed TXT are present.
- Hostname and SSL are both active, and the page says the domain is usable.
- The client receives a full URL with the original path and parameters.
- A main-site fallback is saved and private access keys stay private.
For help, message the administrator with the hostname, error code, record types, and proxy status. Do not send API tokens, passwords, or complete private subscription URLs.