#DNS Nameservers propagation taking too long(72h+)

33 messages · Page 1 of 1 (latest)

weary maple
#

Have you checked the NS servers of your domain to see if they are already set?
If the NS servers of your domain point to Cloudflare, but Cloudflare itself does not work, the error is in the direction of Cloudflare; otherwise in the direction of your registrar.

Depending on the domain extension, you can also do this directly with the publisher of the domain.
Example .de -> denic: https://webwhois.denic.de/

#

If the status on cloudflare switches to "active" the domain is configured properly to use with cloudflare. The propagation of dns depends much on the dns servers used.
After the site switched to "active" it might take up to 48 hours per dns server to forget the old entry. So itsome people might already have the new dns server (when their dns does not have the cached old entry), and some people might still use the old one (as their dns server has a cached old entry)

#

Cloudflare does notice the dns change nearly instant, after the dns entries were changed at the registry. So then the page switched to active yesterday, the registry changed the nameservers yesterday - and the 48 hours started yesterday

#

You can already change them. Depending on the cache they might already work for some user then

#

Varies from client to client

#

If the dns server used by the saas provider does not use the cached old dns servers, yes

#

Correct, and some already by now

#

No problem

weary maple
#

Did you try to ask cloudflare directly? dig @1.1.1.1 NS yourdomain.com

#

nslookup -type=NS yourdomain.com 1.1.1.1 under windows I think

lavish verge
#

What's the domain?

#

sounds like cf ns is set in dns but not in whois/at registrar

fading dune
keen valve
#

you will probably have to ask your registrar if its still not working

#

yeah

#

you entirely misunderstand

#

?discord-support

round basinBOT
#

This Discord is not an official support form. The Community Champions, community members and employees are here because they want to be not because they need to be.
Please do not ping Community Champions or employees for support reasons.

You can open a ticket on the Support Portal if you want official support.

keen valve
#

well ns servers not updating is either you have not actually set the cf ns servers or there is some issue since the changes you have made in the shopify panel are not bein executed

#

nither of which are cf issues

#

ask shopify

#

if they tell you its a cf issue, they are lying to you

keen valve
#

nothing to 2 with cf.

#
Server:        8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
vildedecor.com    nameserver = ns-cloud-b1.googledomains.com.
vildedecor.com    nameserver = ns-cloud-b2.googledomains.com.
vildedecor.com    nameserver = ns-cloud-b4.googledomains.com.
vildedecor.com    nameserver = ns-cloud-b3.googledomains.com.```
#

should be proof enough for them

fading dune
#

who's running shopify? well... who's crawling shopify to its death?

glad coral
#

I have changed ns for 5 domains so far, all the time my ns were switched to cloudflare within 15mins. My domain registrar is Godaddy and I didn't change any other stuffs like that clientupdateprohibited

Try clicking the "Restore Shopify Nameserver" button, wait for 10 minutes then switch to custom nameserver (delete your domain on cloudflare and add it again, you probably see new ns names instead of anahi and tadeo)
-# My knowledge in this area is very limited but I thought this might help

#

No idea lol, but it might work (who knows)

#

Cloud run is by google no? (If yes they probably have ddos protections)

fading dune
#

i fixed it on my own

#

big brain..