Problem with Naked Domain "non www"

Hello,

I have plesk… I’m sorry about that.

First I installed the plesk plugin, before I realized that I couldn’t manage my “naked domain” with this plugin.

So I switched my DNS servers to those of Cloudflare. I have informed the CNAME (Domain name) and A (IP of the server on which the website is hosted).

After a few seconds/minutes, Cloudflare tells me that everything is working.

I then activated the cloud (“Orange cloud”) on the CNAME and A

I set my SSL certificate with Cloudflare in “Full (strict)” mode.

Everything seems to be working? Well, not really. In fact, for some reason I don’t know, Cloudflare Proxy doesn’t work on the “naked domain”. Cloudflare seems to manage DNS well, however the cloud/proxy is only enabled on the www.

Could this be due to a bad Plesk setting because it seems to me that I can’t do better on the Cloudflare side:)?

Whats the domain?

1 Like

Loads fine for me. Also at http://sitemeer.com/#https://kelite.social/

Could it be a DNS propagation issue on your end? Can you post a screenshot?

Could you take a look at this :

VS

For example if I activate the “I’m under attack” mode, it doesn’t matter at all, as if Cloudflare wasn’t there. All requests are sent through my server and not Cloudflare.

Even if you are doing a tracert, the last hostname is my server, not Cloudflare, which is very weird.

Already 24h since I installed Cloudflare.

I dont know what that service does, but as you notice from the link I posted earlier your naked domain does resolve to Cloudflare addresses. So you should be fine in that regard.

My main issue is not with this website. Actually, all Cloudflare’s services are disabled on naked domain. I can even see my server with a tracert.

Again, as I said before, your naked domain is properly behind Cloudflare and resolves to Cloudflare addresses, as evident from the link I posted.

If a traceroute shows your IP address, it is probably aforementioned propagation issue. Simply wait a few hours.

Alright, I will do. Thanks !

Alternatively you can also post the output of these commands. If you dont want your server address revealed, simply redact it where applicable

nslookup kelite.social
nslookup kelite.social 1.1.1.1
nslookup kelite.social 1.0.0.1
nslookup kelite.social 8.8.8.8

ping kelite.social

nslookup kelite.social

Serveur : UnKnown
Address: 192.168.0.254
Réponse ne faisant pas autorité :
Nom : kelite.social
**Address: ******

nslookup kelite.social 1.1.1.1

Serveur : one.one.one.one
Address: 1.1.1.1
Réponse ne faisant pas autorité :
Nom : kelite.social
Addresses: 104.27.156.136
104.27.157.136

nslookup kelite.social 1.0.0.1

Serveur : one.one.one.one
Address: 1.0.0.1
Réponse ne faisant pas autorité :
Nom : kelite.social
Addresses: 104.27.156.136
104.27.157.136

nslookup kelite.social 8.8.8.8

Serveur : google-public-dns-a.google.com
Address: 8.8.8.8
Réponse ne faisant pas autorité :
Nom : kelite.social
Addresses: 104.27.157.136
104.27.156.136

ping kelite.social

Envoi d’une requête ‘ping’ sur kelite.social [****] avec 32 octets de données :
Réponse de X : octets=32 temps=23 ms TTL=54
Réponse de X : octets=32 temps=23 ms TTL=54
Réponse de X : octets=32 temps=23 ms TTL=54
Réponse de X : octets=32 temps=24 ms TTL=54
Statistiques Ping pour 91.121.31.25:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 23ms, Maximum = 24ms, Moyenne = 23ms

Yes, it is a propagation issue. Your local resolver still returns the server IP address instead of Cloudflare’s. Just wait and it should refresh that at some point. Alternatively you can also switch to a public resolver, they are typically faster in that.

Also, you can remove your posting again to make sure the IP does not leak.

thanks, I will let you know Tomorrow if it’s actually working! I changed it more than 24h ago, I will wait an additional day.

I would expect your resolver to have refreshed that within 24 hours. You seem to use a local router as resolver. Can you try restarting that router? Maybe that will clear its cache.

Do you have the same outpout as me with a ping ? I tried it on different network and I still have the same output.

No, I dont. As I said, it resolves fine for me and at http://sitemeer.com/#https://kelite.social/.

Different network but same browser, same machine?

Yes different network, and I’m using the windows cmd console which should not be caching anything ?

The command line shouldnt, but it is still cached by the resolver on that connection you will have the same issue.

What does ipconfig /all return on that other network?

Hold on, A friend of me have tested it on his own machine. It looks like it’s an issue on my end.I will try to resolve this thanks for your help!

This topic was automatically closed after 31 days. New replies are no longer allowed.