Google DIG website recognizes that the nameservers have been changed, but Cloudflare has not seen this for over 6 hours now. Normally it’s almost instant. Is something wrong?
Kindly try to flush the DNS cache for the “NS, SOA, A, AAAA, MX, CNAME” record for your domain example.com (without www prefix) with help of links below:
Cloudflare flush the DNS:
https://cloudflare-dns.com/purge-cache/
Google flush the DNS:
https://developers.google.com/speed/public-dns/cache
Moreover, could be due to the TTL value of 5min-1 hour (300-3600) and up to for specific DNS records, or at least wait for 24 hours if TTL (1440) even good to wait 24 hours per SOA and NS to fully propagate.
If recently added to Cloudflare, you can go with “Re-Check now” to make Cloudflare check the NS records.
1 Like
Thanks, done.
Do you see anything strange in the DNS records?
tungaloy.com
The Cloudflare NS spelling is correct.
SOA is showing Cloudflare also now but my dashboard still says it’s not connected.
dig +short ns tungaloy.com
tina.ns.cloudflare.com.
art.ns.cloudflare.com.
dig +short soa tungaloy.com
art.ns.cloudflare.com. dns.cloudflare.com. 2036398554 10000 2400 604800 3600
I still got returned four nameservers for your domain:
#1: art.ns.cloudflare.com
#2: tina.ns.cloudflare.com
#3: ns1.tungaloy.com
#4: ns6-tk02.ocn.ad.jp
If not already, please remove #3 and #4 and only keep #1 and #2.
Yes, there is some mixed up thing, see here on IntoDNS:
Maybe you listed Cloudflare’s nameservers under “private NS” so you could have ns1.yourdomain.com and ns2.yourdomain.com VS you should list under nameserver for domain, and not private.
Are you on the Free or Paid Cloudflare plan? (maybe using custom name for nameservers - Enterprise plan)
1 Like
WHOIS at your registrar still show your old name servers. Also, keep in mind that name server changes can take up to 48 hours to fully propagate.
This topic was automatically closed after 31 days. New replies are no longer allowed.