Over 24 hours now DNS WONT RESOLVED

DNS won’t resolved despite the fact that my DNS records is showing Cloudflare records. But my IP is still showing my server Ip instead of Cloudflare op

Your DNS records are not proxied. If you want to proxy them over Cloudflare you will need to switch them from :grey: to :orange:.

The domain is already poixed

Not from what I can tell. It still resolves to your actual IP address. The account seems to be right (nameservers match) but it refers to wrong nameservers. So are you sure it is the right Cloudflare account?

Maybe try switching them to :grey: and then back to :orange:.

Okay I will. What if I remove them totally wait till 24hours and create another Cloudflare account

My moves to Cloudflare often take closer to 48 hours.

From my end, it all looks good, except that your Proxy IP address isn’t being pushed out. As long as the Cloudflare Dashboard thinks your name servers are not correct, I don’t think it’s going to work.

Isn’t there an option on that second screen to re-scan for name servers? If it’s not working at the 48 hour mark, open a Support Ticket.

Login to Cloudflare and then contact Cloudflare Support by clicking on the Get More Help button.

I dont think removing will necessarily help. Did you try switching them?

:wave: @gloriaeje7,

For whatever reason your update to your NS records at your registrar has not yet propagated to the root hint nameservers (perhaps an issue at your registrar)?

dig ejesgist.com ns +trace                

; <<>> DiG 9.8.3-P1 <<>> ejesgist.com ns +trace
;; global options: +cmd
. 225888 IN NS j.root-servers.net.
. 225888 IN NS h.root-servers.net.
. 225888 IN NS e.root-servers.net.
. 225888 IN NS g.root-servers.net.
. 225888 IN NS l.root-servers.net.
. 225888 IN NS b.root-servers.net.
. 225888 IN NS m.root-servers.net.
. 225888 IN NS a.root-servers.net.
. 225888 IN NS i.root-servers.net.
. 225888 IN NS d.root-servers.net.
. 225888 IN NS f.root-servers.net.
. 225888 IN NS k.root-servers.net.
. 225888 IN NS c.root-servers.net.
;; Received 228 bytes from in 184 ms

com. 172800 IN NS m.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
;; Received 490 bytes from in 214 ms

ejesgist.com. 172800 IN NS ns4.a2hosting.com.
ejesgist.com. 172800 IN NS ns3.a2hosting.com.
ejesgist.com. 172800 IN NS ns2.a2hosting.com.
ejesgist.com. 172800 IN NS ns1.a2hosting.com.
;; Received 176 bytes from in 134 ms

ejesgist.com. 86400 IN NS ns4.a2hosting.com.
ejesgist.com. 86400 IN NS ns2.a2hosting.com.
ejesgist.com. 86400 IN NS ns3.a2hosting.com.
ejesgist.com. 86400 IN NS ns1.a2hosting.com.
;; Received 112 bytes from in 36 ms

Until that happens and the zone is active Cloudflare will not proxy requests to your origin.


It had propagated earlier. The OP must have changed it back.

1 Like

About ten minutes ago

Updated Date: 2019-07-13T15:43:19Z

For now I just pause Cloudflare and I changed the name server on my end to my hosting name server. If all the Nameserver have been resolved back to my hosting name server. I will add the account again. Will that be good

Again, did you try to switch it? Your setup looked all right and it only seemed as if the proxy status might have got stuck. A simple switch might have fixed that.

Let me change it back

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