I have a problem. I am trying Jelastic provided by Aruba. I've done my tests. I created, deleted environments and on the environments I hooked third level domains. I have a problem, I can no longer associate a third level domain. Does Jelastic tell me it's already in use? I tried to contact my provider's support but they still don't give me an answer. Anyone know anything? Have you ever encountered this problem? The screenshot here
0
votes
2 Answers
0
votes
Since you have a public IP assigned, the domain binding is irrelevant anyway. Just point your DNS to the IP.
Domain binding is only needed to configure the Shared Load Balancers (Jelastic platform infrastructure) to know where to direct traffic when you do not have a public IP.
More details in the documentation: https://docs.jelastic.com/custom-domains/#how-to-bind-domain-to-environment
Note: Custom domain binding via the Jelastic dashboard is unnecessary if public IP is enabled for the environment, as incoming traffic bypasses SLBs.
(That your Jelastic provider's support team couldn't tell you this stuff ought to be worrying!)
0
votes
You don't need to use domain binding if you are assigned an external IP address. You just need to create the correct A record that will point to your ext. IP. We have a bug when the custom domain is not released after deleting the environment (this is just your case). This bug will be fixed in the next platform release.
