3 ms·
The catch is that you must use Cloudflare's nameservers [0]: 6.1 Nameservers. Registrant agrees to use Cloudflare’s nameservers. REGISTRANT ACKNOWLEDGES AND
by timbowhite 4y ago
The catch is that you must use Cloudflare's nameservers [0]:
6.1 Nameservers. Registrant agrees to use Cloudflare’s nameservers. REGISTRANT ACKNOWLEDGES AND AGREES THAT IT MAY NOT CHANGE THE NAMESERVERS ON THE REGISTRAR SERVICES, AND THAT IT MUST TRANSFER TO A THIRD PARTY REGISTRAR IF IT WISHES TO CHANGE NAMESERVERS.
[0] https://www.cloudflare.com/domain-registration-agreement/ https://www.cloudflare.com/domain-registration-agreement/
- farseer 4y agoThis usually isn't a problem, you can point the DNS to any hosting service you want. Its a pain to setup every single record of-course.
- SahAssar 4y agoThat's extremely weird. Is there a publicly stated reason for it?
- Alupis 4y agoPeople generally use 3rd party Nameservers when their Registrar is unreliable or "old school". Most dot-com era web companies used Network Solutions back in the day - and many still use them. However, DNS updates sometimes take hours, their interface is cumbersome, etc. It's become quite common to use someone like Cloudflare for Nameserver/DNS duties (among other things) and keep your registrar where you like.