Getresponse subdomain issue

Zero Trust 1.1.1.1
1

I came across this posting from earlier this year I’m currently have the same issue but i was unable to see a reply or answer and the topic is closed.

Hi Guys,
I am very desperate!

I am using Cloudflare as a beginner user but I am quite able to set up a cname and usually it works.

Unfortunattelly I am not able to make it working with getResponse service.

I am trying to create a custom domain on getResponse where there will be my landing page.
Info seems very easy…

  1. Log in to your hosting control panel.

In the domain settings section, look for the DNS settings.


3. ```
Once you’re in the settings section, create a CNAME record for your subdomain that points at **squeeze.gr8.com**

So I have created 2 cname

  • cname -> download > value -> is an alias of (see point 3)
  • cname -> www.download > value -> is an alias of (see point 3)

After 48 hours I have the same issue…
trying to go to http://download.mydemopage.com I am redirected to landing page not found…

Off course I have created the subdomain on the getResponse space and getResponse team says that both (Cloudflare and getResponse) settings are corrects but there could be some issue on Cloudflare end.

what do you think?
Thanks a mil for your help.
It is very very appreciated

2

I’m experiencing this same issue with Cloudflare and GetResponse - has anyone had a success with this issue? …GetResponse Support has been no help… this is the only post on the web that I can find on this topic…

Thanks in advance if anyone can assist!

3

I have the same issue.
Seems that nobody is interested in resolving

4

Hi @richard37,

Can you see if the record is :orange: or :grey:, if :orange: click it to turn :grey: so it won’t be proxied by Cloudflare and see if that helps.

If it doesn’t work :grey:, it doesn’t look like an issue on Cloudflare’s side as they won’t be proxying it.

5

I already switched of proxy.
I have exactly the same adjustments like in godaddy.

Actually they were copied automatically

I waited 24 hour but nothing happened.

That’s a long time being down for my landingpage.

Now I set it all up again. To make it work.

But the thing is that the adjustments worked perfectly before on godaddy. And ow their still the same

6

If it worked in GoDaddy, all the records were copied over correctly and they are set to :grey:, Cloudflare shouldn’t be making any difference on this.

Can you try psusing Cloudflare completely to see if this resolves it?

You can pause Cloudflare from the Overview tab of the Cloudflare Dashboard, bottom right under Advanced Actions.

If the issue persists after Cloudflare has been paused, it means that there is an issue with your origin, Cloudflare is only operating as your DNS provider while it is paused.

7

I dont understand.
The nameserver is still specified with the values og CL
Why should it suddenly start working then.

I tried pausing and nothing happened.
Maybe I have to wait a while. So Ill check again in maybe 20 min.
As I wrote. I deleted all old subdomai links in Getresponse and set them up again. so anyway if I pause CL what hapens then whit the DNS entries. where will they be? I can access in Godaddy anymore.

So Ill wait, because eveything is set up new. I guess the change has to propagate trough the web

8

When you pause Cloudflare, the DNS will still be at Cloudflare, but all other services will be disabled. If it works then, it’s probably a Cloudflare issue. If it still doesn’t then it’s either an issue with the provider or incorrect DNS records.

9

Ok, I did it
And now as CL is paused everything is working

10

So how would I manage to get it working with CL?

11

So as Getresponse was working with CL on pause, and also the Getresponse landingpage started loading after 20 min y tried switching CL back on.
Now after 30 min the landingpage is not loading.
So Cloudflare is not working with getresponse?

12

If it does not work when proxied through Cloudflare, it may be that you have to disable Cloudflare for that subdomain, maybe they check for the CNAME which, when proxied, shows Cloudflare IPs instead.