nameserver not yet updated after lot of time
Pending nameserver update for a long time even though i have updated nameserver in the registrar , it has been a long time still nameserver not yet updated for
clipsync.in.net
clipsync.in.net
CTech Email: https://whois.centralnic.com/contact/clipsync.in.net/tech
Name Server: DNS3.BIGROCK.IN
Name Server: DNS2.BIGROCK.IN
Name Server: DNS1.BIGROCK.IN
Name Server: DNS4.BIGROCK.IN
Name Server: ALEENA.NS.CLOUDFLARE.COM
Name Server: NASH.NS.CLOUDFLARE.COM
You added them but didn't remove the others
Name Server: DNS3.BIGROCK.IN
Name Server: DNS2.BIGROCK.IN
Name Server: DNS1.BIGROCK.IN
Name Server: DNS4.BIGROCK.IN
Name Server: ALEENA.NS.CLOUDFLARE.COM
Name Server: NASH.NS.CLOUDFLARE.COM
You added them but didn't remove the others
Cremove all the bigrock ones
Fdone so it will take a day or two right ?
Cusually way quicker, few hours, sometimes even less then an hour but it depends the TLD. I don't have any experience with
in.netClooks like some of their NS are already updated
Cyou should get an email from CF when it sees it as active
Fas far as i know
The .IN.NET is a sub-domain of .NET and is presented as an unofficial alternative for India.
The .IN.NET is a sub-domain of .NET and is presented as an unofficial alternative for India.
Fok will check
Fyep got mail thank you so much man
Fi had another domain dhatrish.online with the same issue i have removed bigrock name servers it should also get verified quickly right ?
CLike I said above, it really depends on the TLD how fast they update
Csome ccTLDs like ms take ages
CIf you have dig/a linux machine you can check yourself like this:
chaik@ash:~$ whois dhatrish.online | grep 'Name Server'...
Name Server: ALEENA.NS.CLOUDFLARE.COM
Name Server: NASH.NS.CLOUDFLARE.COM
chaik@ash:~$ dig online ns +short
a.nic.online.
b.nic.online.
e.nic.online.
f.nic.online.
chaik@ash:~$ dig dhatrish.online @a.nic.online ns
...
;; AUTHORITY SECTION:
dhatrish.online. 3600 IN NS dns3.bigrock.in.
dhatrish.online. 3600 IN NS dns1.bigrock.in.
dhatrish.online. 3600 IN NS dns2.bigrock.in.
dhatrish.online. 3600 IN NS nash.ns.cloudflare.com.
dhatrish.online. 3600 IN NS aleena.ns.cloudflare.com.
dhatrish.online. 3600 IN NS dns4.bigrock.in.
Crepeat for each of the online ns (a, b, e, f) to get an idea for propagation
Conce those are updated it's just waiting for CF to recheck
MIf it helps you can also do a DNS Check here https://mxtoolbox.com/SuperTool.aspx?action=a%3aclipsync.in.net&run=toolpage or by doing dig command https://developers.cloudflare.com/dns/troubleshooting/faq/#where-can-i-find-my-cloudflare-nameservers
As chaika mention and for reference you can use this dev doc that explains the registrar update on the nameservers and how to locate it
https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/#update-your-registrar
Hope it helps
As chaika mention and for reference you can use this dev doc that explains the registrar update on the nameservers and how to locate it
https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/#update-your-registrar
Hope it helps
Cloudflare Docs
Yes. Cloudflare offers free DNS services to customers in all plans. Note that:
Cloudflare Docs
If you want to use Cloudflare as your primary DNS provider and manage your DNS records on Cloudflare, your domain should be using a full setup.
CThose are helpful links! But I would be careful about mxtoolbox and other dnschecker websites
Cthe problem is, mxtoolbox/dnschecker/etc are recursive resolvers
Cpeople mess up and will update their actual DNS but not their registrar nameservers, which will look fine in mxtoolbox but not activate their domain in NS
(ex: their domain nameservers point to aws route53, route53 has ns records for Cloudflare, dnschecker will show the user what route53 returns and not the actual domain's nameservers)
(ex: their domain nameservers point to aws route53, route53 has ns records for Cloudflare, dnschecker will show the user what route53 returns and not the actual domain's nameservers)
Cwhen debugging your nameservers, you want to either use
whois <domain> or specifically query the authoritive nameservers for the TLD (which also helps check propogationMI do understand, but mxtoolbox also have whois option and many other useful options just saying but I do agree with you!
https://mxtoolbox.com/NetworkTools.aspx
https://mxtoolbox.com/NetworkTools.aspx
