Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Unable to use CNAME records when setting up domain for Liferay SaaS

Written By

Justin Mann

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • When going Live on Liferay SaaS, one of the steps that is required is to create a CNAME record for the domain associated with the project (<yourprojectid>.lxc.liferay.com), which is provided during the provisioning process.
    • Some DNS providers do not offer CNAME records to base domain names.

Environment

  • Liferay SaaS
  • Liferay DXP 7.4

Resolution

  • Although it is best practice and an industry standard to use the CNAME record when setting up the domain for Liferay SaaS, sometimes it is not possible to follow that recommendation due to different extenuating circumstances.
  • In those cases, Liferay SaaS can also be setup to work with an A record that is connected to a IP Address.
  • The downside for using the A record instead of the CNAME record is that it affects disaster recovery capabilities.
    • If using the CNAME record, in the event of a severe GCP outage, Liferay can handle everything on our end to restore service
    • However, if using an A record, tighter collaboration is required between Liferay and the customer. In the event of a severe GCP outage, Liferay would need to request the customer to update the A record to a potentially new IP address before the service can be restored.
  • To implement this, the A record just needs to point to the appropriate IP address, and then the customer can update the virtual host name in the portal site configuration to match.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?