Issue on nested shared domains

Carlo Alberto Ferraris

Due to internal regulations our users need to deploy apps on two wildcard domains, where the second is the a subdomain of the first one, e.g.:
- *
- *

We registered both as shared domains and they work fine, but we have run now into a surprising behavior. Turns out it's not allowed to register route

$ cf create-route my-space --hostname B
Creating route for org my-org / space my-space as my-user...
Server error, status code: 400, error code: 210001, message: The route is invalid: host domain_conflict

I agree that using nested shared domains may not be the best of designs, but is the above behavior expected? At the DNS level this is allowed, and I don't really see a reason why it shouldn't be allowed in CF...


Join to automatically receive all group messages.