Domain abc.com is not reflecting to "Verified" status in Adobe Cloud Manager | Community
Skip to main content
NageshRaja
NageshRaja
Level 5
June 2, 2025
Solved

Domain abc.com is not reflecting to "Verified" status in Adobe Cloud Manager

  • June 2, 2025
  • 2 replies
  • 596 views

Hey Guys,

 

We have a domain abc.com which is managed by the client.

We have uploaded the customer managed certificate but the domain is still not getting verified.

 

The setup works correctly as the requests hit on domain abc.com are served by AEM Publisher.

The setup uses WAF which has rewrites configured to valid AEM Publishers with X-Forwarded-Host header set to abc.com and correct X-AEM-Edge-Key configured.

 

However, when we navigate to the "Domain Settings" we see the below domain as "Not Verified"

Same under "Domain Mappings" we see the following - 

Interesting observation is we have already configured the steps mentioned in "Go Live" - 

a. Configure A Record - Login to your Domain Registrar and create an A record to point to all the IP addresses listed

b. Configure CName - Add "cdn.adobeaemcloud.com" CNAME record on abc.com.

 

However in out case the cdn.adobeaemcloud.com didn't work. We had to configure the publisher "publish-p<pid>-e<eid>.adobeaemcloud.com for the flow to work.

 

Can anyone help why the domain and mappings are not showing to resolved status?

And why the CName didn't work for cdn.adobeaemcloud.com but it worked for publisher adobeaemcloud.com?

 

Thanks,

Nagesh

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Rohan_Garg

Hey @nageshraja,


cdn.adobeaemcloud.com is a generic domain - Its not a valid origin!

The actual origin you configure in your CDN is publish-p<PROGRAM_ID>-e<ENV_ID>.adobeaemcloud.com
The DNS points to your CDN.

Can you conduct a smoke test using the below?

curl -I https://abc.com -H 'x-aem-debug:edge=true' 
The HTTP headers should confirm the route.

 

Thanks,

Rohan Garg

2 replies

AmitVishwakarma
Community Advisor
AmitVishwakarmaCommunity Advisor
Community Advisor
June 3, 2025

Hi @nageshraja ,

    NageshRaja
    NageshRajaAuthor
    Level 5
    June 3, 2025

    Hi @amitvishwakarma,

     

    Thanks for replying!

    If the DNS must necessarily point to Adobe CDN then why does the Customer managed CDN points to AEM managed CDN says "Point your CDN to the Adobe CDN’s ingress as its origin domain. For example, publish-p<PROGRAM_ID>-e<ENV-ID>.adobeaemcloud.com"

    It doesn't mention cdn.adobeaemcloud.com as the ingress
    Moreover when we configure cdn.adobeaemcloud.com as the ingress then the request doesn't come to publisher.

     

    Finally since the request routes from WAF to Adobe CDN shouldn't the dig give imperva as shown below?

    naga_krish@EPUGW0238 ~ % dig www.abc.com CNAME +short
    nsi9go2.ng.impervadns.net.

    Rohan_Garg
    Community Advisor
    Rohan_GargCommunity AdvisorAccepted solution
    Community Advisor
    July 31, 2025

    Hey @nageshraja,


    cdn.adobeaemcloud.com is a generic domain - Its not a valid origin!

    The actual origin you configure in your CDN is publish-p<PROGRAM_ID>-e<ENV_ID>.adobeaemcloud.com
    The DNS points to your CDN.

    Can you conduct a smoke test using the below?

    curl -I https://abc.com -H 'x-aem-debug:edge=true' 
    The HTTP headers should confirm the route.

     

    Thanks,

    Rohan Garg

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    June 17, 2025

    @nageshraja Did you find the suggestion helpful? If you need more information, please let us know. If a response resolved your issue, kindly mark it as correct to help others in the future. Alternatively, if you discovered a solution on your own, we'd appreciate it if you could share it with the community. Thank you.

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...