Nameserver change has been implemented but Cloudflare did not detect the change

I have a problem regarding nameserver and Cloudflare.

I have set the nameserver properly and the changes show (in this case I am using whatsmydns.net) and yet Cloudflare is still asking me to change the nameserver. I would like to know whether if I am on the right track and I just need to wait or I have made some mistakes while setting my domain up.

I have checked this post but the problem resolved as soon as the namespace changes reflect on whatsmydns.net (which in my case it did not).

link for the website: terjumpa.com

Thanks in advance.

Seems to me like you have entered or updated the NS type of DNS record, rather than the domain nameservers at your domain registrar?

Using DNS checker - online tool - I do see Cloudflare nameservers and on a few resolvers the old values.

Furthermore, using DIG command for NS type I see Cloudflare nameservers too.

But using the WHOIS command I see the old nameservers → last updated 2020-08-14.

1 Like

I did it on AWS Route 53, inside the NS record details as was instructed by my manager.
How exactly do I find out my domain registrar so that I can change the actual domain nameservers?

That seems to be the DNS record interface at hosting provider - AWS.

May I ask if you followed the instructions from below article to change your domain nameservers?:

Maybe the DNS Holdings or DirectNIC?

You could also try by searching your e-mails to find anything associated with your domain name, or “renew”, etc.

I did not follow the article as my domain is not listed inside the registered domains, instead I just change the details of nameserver in “hosted zone” located on the Route 53. I think that the domain is not registered by AWS but some other registrar.

1 Like

It looks correct to me now. Is it working for you?

1 Like

Finally it worked, Cloudflare has already activated. Thank you so much for helping.

1 Like

Just to give feedback, I see things still in propagation so I would wait few more hours just in case and/or make sure to have SSL certificate and HTTPS configured in place :wink:

Cached old?

Cloudflare IP:

0003

Something in between:

For now there are no plans on adding SSL certificate to this site as the site is only for testing Cloudflare CDN and Workers (I am very new to this platform). Is SSL a requirement for those services? and if yes, is it possible to get one for free? I have read that Cloudflare can give SSL certificate for free but I don’t really know how.

Okay, but you might have to:

  1. Select the “Off” option under the SSL/TLS tab
  2. Disable the Always Use HTTPS option
  3. Disable the Automatic HTTPS Redirection option
  4. Disable the Universal SSL option? → I am not sure about this, as you might end up having some issue later, possibly …

Does it mean you currently do not have an SSL certificate at your origin host/server?

Nevertheless, I might have a different point of view and a perspective on this, so I cannot resonate if that’s the correct way to do it, even cannot vote for using :orange: without the HTTPS (SSL).
This might also impact the thing of not having the performance and features enabled like Brotli, HTTP/2, etc.
I do not see it as an option at all. Why using proxied mode :orange: then?

Furthermore, I haven’t used Cloudflare Workers without HTTPS so I cannot confirm if that works at all. May I advise you to use search :search: for any possible answer on this.

In terms of a “Cloudflare free SSL”, more information can be read at the below article:

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

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:

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

Kindly, allow me to ask @sandro to check this and re-read as he is more experienced in security/SSL field and I believe he could provide you with the correct answer on this one.

1 Like

Ohh, more experienced I don’t know, he’s just mostly wielding the Mighty Sword of Encrypted Strictness :wink:

Everything you said seems just right to me. What the OP has read will be the usual myth about proxy certificates being enough, but then we all know that story, do we not? :smile:

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.