fly launch when confirmed to modify default settings redirects to fly.io/cli/launch/<hash>. When entering various app names (log-shipper, logs-shipper) I get an error 'logs-shipper' is already taken, which is not true obviously.
I’m wondering why this happens and if we can get this fixed.
Hi… Possibly I’m taking your example too literally, but app names are a global namespace—shared amongst all of Fly.io’s customers. Anyone else could have tried that same sequence, too, 
.
I do see AAAA records for both of those:
$ fly dig log-shipper.fly.dev
log-shipper.fly.dev. 300 IN AAAA 2a09:8280:1::3:138d
$ fly dig logs-shipper.fly.dev
logs-shipper.fly.dev. 300 IN AAAA 2a09:8280:1::42:522e
People have asked in the past for reserved prefixes and so on, but it’s still on the wishlist so far…
$ fly dig orange-hat-dog-logs-shipper.fly.dev
;; opcode: QUERY, status: NXDOMAIN, id: 15506
That one is free, at least, but act quickly!
Oh welp, I completely forgot about this thing 
Perhaps it’s counter-intuitive that these are unique globally even if you’re not planning on using any external domains
Thank you!
I’m in the habit of prefixing all apps by org name, but it’d be nice to have that prefix be automated for sure.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.