Invalid landing page error | Community
Skip to main content
ishi1234
New Participant
January 23, 2024
Solved

Invalid landing page error

  • January 23, 2024
  • 3 replies
  • 4293 views

Hi everyone, 

 

My client has  now decided on the sub domains for the Adobe Marketo Landing Page and Email tracking domain. We have asked IT  with adding the following CNAME record for landing page in DNS records. 

DNS Entry (CNAME) for lp.example.com, pointing to yyy-xxx-000.mktoweb.com. When i try adding the landing page domain in marketo it gives me an error, invalid landing page domain and It is already been 2 weeks.  Can someone guide me what is wrong . 

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 SanfordWhiteman

@ishi1234, If it was due to the delay in DNS propagation, it should likely have been solved by now. DNS propagation typically takes between 24 and 48 hours, though it can sometimes stretch to 72 hours in rare cases. You can raise a support ticket if you continue to face this issue, and they can check it on their end and reach out to Cloudflare regarding this if required.

 

Also, while configuring SSL certificates is a good practice for securing your landing pages, it's not directly related to the current DNS resolution error.


More to the point, at the current time lp.stressless.com is set up as an alias for 853-xwi-508.mktoweb.com.

 

There’s nothing wrong with the replication of that CNAME RR itself.

 

However, the CNAME 853-xwi-508.mktoweb.com does not exist now, so it’s clear that you need to open a support ticket:

; <<>> DiG 9.16.24 <<>> 053-xwi-508.mktoweb.com. ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 23966 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;053-xwi-508.mktoweb.com. IN A ;; AUTHORITY SECTION: mktoweb.com. 894 IN SOA ns1.marketo.com. ops.localhost. 3040351596 300 300 604800 900

 

3 replies

uditmathur
Community Manager
January 24, 2024

Hi ishi1234,

 

I have also faced this issue with one of my clients & this happens when the DNS is not properly propagated. 

I will suggest to reconfigure DNS & try, this might take up to 48 hours. Also recheck if SSL has been configured properly.

If the issue still persist it will be best to raise a ticket with Marketo support.

SanfordWhiteman
New Participant
January 24, 2024

Doubt it has anything to do with propagation of a new domain (note “propagation” is kind of a misnomer except for the very specific connection between a registrar and the root nameservers). But that’s why I asked for the actual DNS record so we can check.

 

It can have to do with inconsistencies across NSes, but that isn’t propagation so much as replication.

 

It can’t have anything to do with SSL because you can’t get an SSL cert provisioned by Marketo until DNS is correct in the first place.

Michael_Florin-2
New Participant
January 23, 2024

I experienced this the last two times I tried to add an LP domain. I believe it's a Marketo bug and only Support can help you.

SanfordWhiteman
New Participant
January 23, 2024

Actually think it happens because of specific responses from your nameserver(s), that’s why I wanted to see the real domain.

 

Recently I set up a domain on my own nameserver (SimpleDNS) and it failed, while the exact same zone & records on AWS Route 53 succeeded.

SanfordWhiteman
New Participant
January 23, 2024

In this case, it's necessary to provide your actual DNS entries so we can double-check them for you.