Long alias names deploys with no errors, but does not work

Support
1

My netlify site name:

https://long-names-bug.netlify.app

For some time (a year maybe?) when I deploy with longer aliases names, the process seems to finish just fine, but I cannot open the page.

Logs:

dzek@dzek-garuda-2nd:/Projects/tmp/mh$ pnpm dlx netlify deploy --dir=out --alias 2025-09-12-v-10-testnet-some-longer-description-of-the-release
​
Netlify Build                                                 
────────────────────────────────────────────────────────────────
​
❯ Version
  @netlify/build 35.1.6
​
❯ Flags
  accountId: 62a1bda2a0bc894c0c49079f
​
❯ Current directory
  /Projects/tmp/mh
​
❯ Config file
  No config file was defined: using default values.
​
❯ Context
  production

Deploying to Netlify
────────────────────────────────────────────────────────────────

Deploy path: /Projects/tmp/mh/out

✔ Finished uploading blobs to deploy store
✔ No cached functions were found
✔ Finished hashing 
✔ CDN requesting 2 files
✔ Finished uploading 2 assets
✔ Deploy is live!
​
Netlify Build Complete                                        
────────────────────────────────────────────────────────────────
​
(Netlify Build completed in 3s)

🚀 Deploy complete
────────────────────────────────────────────────────────────────

   ╭─────────────────────────────────────────────── ⬥  Draft deploy is live ⬥  ───────────────────────────────────────────────╮
   │                                                                                                                          │
   │   Deployed draft to https://2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app   │
   │                                                                                                                          │
   ╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

Build logs:         https://app.netlify.com/projects/long-names-bug/deploys/68c3f8edc7f5564d17f4db52
Function logs:      https://app.netlify.com/projects/long-names-bug/logs/functions?scope=deploy:68c3f8edc7f5564d17f4db52
Edge function Logs: https://app.netlify.com/projects/long-names-bug/logs/edge-functions?scope=deployid:68c3f8edc7f5564d17f4db52

If everything looks good on your draft URL, deploy it to your main project URL with the --prod flag:
netlify deploy --prod

And here’s the link that won’t open

https://2025-09-12-v-10-testnet-some-longer-description-of-the-release–long-names-bug.netlify.app

Error is:

This site can’t be reached

2025-09-12-v-10-testnet-some-longer-description-of-the-release–long-names-bug.netlify.app’s server IP address could not be found.

Try:

ERR_NAME_NOT_RESOLVED

I can’t wget it either or ping:

dzek@dzek-garuda-2nd:/Projects/tmp/mh$ wget https://2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app
--2025-09-12 12:45:32--  https://2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app/
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving 2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app (2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app)... failed: Name or service not known.
wget: unable to resolve host address ‘2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app’

dzek@dzek-garuda-2nd:/Projects/tmp/mh$ ping 2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app
ping: 2025-09-12-v-10-testnet-some-longer-description-of-the-release--long-names-bug.netlify.app: Name or service not known

I think the DNS thing that resolves aliases on your side is broken, it forcibly limits the length of the domain.

2

Not a Netlify issue, so this:

is incorrect. It’s what the RFC dictates:

image
image1274×830 66.4 KB

1 Like
3

Thanks for you answer. Maybe I remember it wrong then.

How about improving the cli anyway, so it rejects too long aliases immediately instead of doing all the process and pretending it works?

5

Hi, @jacek.nowacki. An issue has already been filed for that exact issue. If there are other questions or concerns, please let us know.