8 Replies Latest reply on Feb 10, 2020 3:12 PM by r0j

    vRA 8 - alternative DNS name

    BenzB Lurker


      I've deployed VRA8 using our company server naming standards as hostname.

      Howerver i'd like to allow user to acces the portal using a more friendly DNS name.

      So I created a host A dns record and also add it as an alternative name in my VRA certificate.

      The problem is that VRA return 404 error when access using that new record, it seems that the webserver deny the request since it doen't know that new record.

      I didn't find any information about that particular case in kb/doc.

      Is it supported ? if yes how can it be achieved ?

      Thanks in advance for your help.



        • 1. Re: vRA 8 - alternative DNS name
          daphnissov Guru
          Community WarriorsvExpert

          This was never supported in vRA 7 so I doubt it's possible in 8.

          • 2. Re: vRA 8 - alternative DNS name
            KocPawel Hot Shot

            If you want to use friendly name I would recommend to use some load balancer like NSX (Record A with friendly name point to LB and LB redirect users to correct URL). vRA supports also F5 and Netscaler.

            Probably you can use some open source LB like HAproxy but remember that it is not supported.


            In vRA 7 record A in DNS is not sufficient because you need to point A record to long url (https://<vra>/vcac/org/<tenant>

            I don't know how vRA 8 works but I suppose that there is the same problem.

            • 3. Re: vRA 8 - alternative DNS name
              KocPawel Hot Shot

              Ok, I've read once again what you did and I've checked that in vRA8 url is just simple hostname.


              Check this:

              1) You have record A and PTR that correspond with you hostname for example vra.your.domain

              2) Create CNAME (not record A) with friendly name for example: cloud.you.domain and point to record A vra.your.domain


              Of course friendly name should be included in SAN (Subject Alternative Name).

              Check and give me a feedback I am curious.

              • 4. Re: vRA 8 - alternative DNS name
                BenzB Lurker


                I also did some test using a cname but its gives the same error "404".

                I guess its should work using any kind of load balancer but it will be a little over kill in my business case since its a small deployment with only one server.

                • 5. Re: vRA 8 - alternative DNS name
                  Zueritram Novice

                  Hi Benjamin


                  Sadly they havent thought of that. So it is currently not possible, unless you deploy it HA, because there you need a load balancer.

                  It worked in vRA 7 like a charm and was also our best practice if you went with a single deployment, so you could scale out afterwards to an HA deployment.

                  Please create a feature request to help to raise the awareness on the VMware side.


                  Cheers Philippe

                  • 6. Re: vRA 8 - alternative DNS name
                    gradinka Master
                    VMware Employees

                    TBH they have thought of that, but let's say there are some technical challenges to it ...


                    Using LB is the option at the moment.

                    • 7. Re:vRA 8 - alternative DNS name
                      RonPSSC Enthusiast
                      You could always create a virtual website using IIS or some other web component (Apache) and have that virtual server, which is mapped to a "friendly Name" of your choosing, to "redirect" to your actual vRA Porrtal.
                      • 8. Re:vRA 8 - alternative DNS name
                        r0j Enthusiast

                        We are doing this for a vRA 7.6 environment using IIS.


                        You will need to dedicate an IP address for this, the create a DNS host record for your friendly name,


                        vra.org.com etc...


                        Bind the IP for your friendly name to the IIS server, then create an HTTP redirect, and paste the URL for your vRA site in there.


                        When you go to vra.org.com in our 7.6 case, it redirects to https://vraserver/vcac/org/tenant/#csp.catalog.selfservice.cilist


                        no certificate errors no san required.


                        As others have suggest above, a load balancer / application delivery controller like F5 Netscaler or NSX will do this for you, provided one is available.