Unable to select CNAME when binding a custom domain to a service; system forces A record configuration

Resolved

Mmis_一方DEVELOPER5/6/2026

I want to bind a subdomain, but when binding a custom domain to my service, I cannot select CNAME; the system forces me to set an A record. How can I use CNAME instead?

Also, the official documentation mentions setting up a CNAME, so I'm not sure why I am being forced to use an A record.

Additionally, although I have successfully bound the domain using an A record, I would prefer to use CNAME to avoid exposing the IP address. Could you please assist with this? Thank you!

2 Replies

JZJiyuan ZhengEMPLOYEE5/6/2026

Hello,

TL;DR: Using CNAME is supported, whether you are using a shared cluster or a dedicated server. If you cannot find the CNAME option in the dashboard, it is because the UI text for that option is not labeled "CNAME"; instead, it is called:

"Redirect all requests to another domain"

It is located within the custom domain binding settings screen. You can enable that option to point your domain to another domain (usually cname.zeabur.app) via CNAME.

Please try changing your DNS to CNAME and see if it works smoothly. If you still encounter issues while using the "Redirect all requests to another domain" option in the dashboard, please take a screenshot of what you see and send it to me so I can continue to assist you.

AAnonymous5/10/2026

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.

This issue has been marked as resolved

New replies are disabled for resolved issues.

Forum

2 Replies