Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Why was my custom domain rejected by Liferay PaaS?

Written By

Albertinin Mourato

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability 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

  • Why was my custom domain rejected by Liferay PaaS?

Environment

  • Liferay PaaS

Resolution

  • If you have configured your domain but Liferay PaaS still rejects it, there might be several reasons for that. For example, if the domain cannot pass DNSSEC validation, it will be rejected. To check it, you may use some of the publicly available tools, like Google Public DNS, dnssec-debugger or DNSViz.
  • When you configure the name servers of the domain to be some of Liferay PaaS name servers, it may take more than one hour for the change to be propagated. You can verify if the process has finished by checking the results of the following two commands: dig NS yourdomain or dig +trace NS yourdomain. The displayed server name of your domain should be some of Liferay PaaS servers name.

Additional Information

  • For more information about how to use Custom Domains, see our documentation.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?