Created 3 subdomain A records on CloudFlare, only 1 works as expected

[user22154]

I created 3 subdomain A records pointing to the same domain. All records point to the same IP address:

a1.testdomain.com
a2.testdomain.com
a3.testdomain.com

The first added record a1.testdomain.com works as expected - I can ping it and when go to it with the browser I get the correct response.

Second and third records didn’t work. The second and third records a2.testdomain.com and a3.testdomain.com are pointing to an unknown IP address, probably a Cloudflare proxy server?!

When I try them on the browser, It gives me page not working. It is not resolving to the correct IP.
Is there something else I need to do? It’s been about 1 hour but no luck. Will this be updated after a few hours? Or, is there a step I missed?

[fritex]

@user22154

are pointing to an unknown IP address, probably a Cloudflare proxy server

If the hostname (DNS record) is proxied and set to , yes it is proxied via Cloudflare and should resolve to the Cloudflare IP.

@user22154

It gives me page not working

May I ask what is the error number?
Can you share a screenshot of this error?

Were your sub-domains secured with the SSL certificate before moving/adding them to Cloudflare and have you got valid and installed SSL certificate covering them?

Have you tried using a different Web browser, or a Private mode (Incognito)?
Maybe mobile data (4G LTE, cellular data) if anything different?

• if it could be due to the DNS propagation / cache …

[user22154]

Here is the error:

The strange thing is the 3 A records were entered in exact same way. 1 works 2 don’t

I tried edge and tried incognito on chrome. tried another computer.
Its a mystery to me. I really want to use Cloudflare.

[user22154]

could this be because of the old A records? I deleted the old records from directnic a couple hours ago.

[fritex]

Thank you for feedback.

Unfortunately, I can reproduce it too at my end.

@user22154

1 works 2 don’t

Seems like those 2 sub-domains didn’t yet got/generated an SSL certificate at your origin host/server, or if you are using cPanel then it’s not generated (via AutoSSL).
If so, make sure both sub-domains are temporary unproxied and set to (DNS-only).
Wait for a few minutes, then generate an SSL certificate for them.
After you confirm they are working fine over the secured HTTPS connection, switch back to proxied and .
Set SSL/TLS to Full (Strict) SSL at Cloudflare.

From the screenshot you’ve posted, ERR_TOO_MANY_REDIRECTS indicates to me like you are either:

1. Redirecting HTTP to HTTPS at your origin host/server
2. Not having an valid and installed SSL certificate for this sub-domain
3. Wrong SSL option is selected under the SSL/TLS tab of Cloudflare dashboard → is it on Flexible SSL?

Community Tip - Fixing ERR TOO MANY REDIRECTS

Error Try the suggestions in this Community Tip to help you fix ERR TOO MANY REDIRECTS. Background If your SSL setting on the SSL/TLS app is Flexible and if your origin server is configured to redirect HTTP requests to HTTPS, server responses back to Cloudflare are encrypted. Since Cloudflare is expecting HTTP traffic, it keeps resending the same request, resulting in a redirect loop. This causes browsers to display “The page isn’t redirecting properly” or “ERR_TOO_MANY_REDIRECTS” errors. [D…

Here is a way to re-check if you correctly setup the SSL for your domain with Cloudflare:

Step 2: Setting up SSL with Cloudflare

This tutorial covers getting SSL working with Cloudflare in various different scenarios. This assumes you already have your website set up on Cloudflare with all your DNS records set to , if not - please visit Step 1. Do you want the website to use HTTPS?

Yes

Do you already have a valid SSL certificate installed on your server (i.e. does it already load over HTTPS with a )? Yes If your website already works over HTTPS, you can just set your SSL mode in Cloudflare to Full (strict)…

In case you do not have an SSL certificate, you can use Cloudflare SSL, if so, kindly make sure you follow the instructions as follows on the below article to setup an SSL certificate using Cloudflare Origin CA Certificate:

• https://developers.cloudflare.com/ssl/origin-configuration/origin-ca

Last but not least, kindly have a look here for more information regarding correct SSL settings at the SSL/TLS tab on Cloudflare dashboard:

Why you should choose Full Strict, and only Full Strict

Unencrypted & unverified connections Imagine you open Paypal and suddenly get that warning [image] Would you continue? Probably not. For decades leaders in IT security have advocated that people upgrade their sites from unencrypted HTTP to secure HTTPS. And for a reason, everything you send via an HTTP connection is sent in plain text and can be intercepted at any point between you and the server. Equally, you’d probably not proceed if you got such a warning, right? [image] That’s when th…

[user22154]

I’m working directly on the servers. No cpanel.

my SSL certificates are up to date with certbot.
SSL setting on Cloudflare are set to flexible.

before I switched my name servers and DNS records from directnic to Cloudflare, everything was working as expected.

Is certbot certificates the problem? should I delete certbot certificates ? before following your instructions?

[fritex]

@user22154

I’m working directly on the servers. No cpanel.

@user22154

my SSL certificates are up to date with certbot.

Great!

@user22154

SSL setting on Cloudflare are set to flexible.

Can you switch to Full (Strict) SSL and re-check a minute-two later for any changes?

@user22154

should I

There is no need to do it if you have valid and installed certbot (Let’s Encrpyt) SSL certificate for your sub-domains at your server.

[user22154]

All right that was it. It is working now. I didn’t understand the SSL settings.

Thanks for your help