It is as I say it is. They are a "middle man." When you make a request to your domain, it hits your domain register first. Then from there it's routed to CloudFlare and then CloudFlare contacts your host.
I've read both articles and I'm properly setup.EA117 wrote: ↑Fri Mar 01, 2019 5:53 pmI believe it's accurate to say that if you have done all of the steps, you have switched over to using Cloudflare for your DNS services, too. Which "makes sense", given that one of the DDoS protections they're intending to provide is DNS flood protection, and they couldn't do that if you were still using your own DNS services.
If you're on a plan where you've intentionally setup Cloudflare by just pointing your own existing DNS records to Cloudflare, the primary caveat is that they won't be able to provide any DNS service-level protections.
Your registrar is used to list the nameservers, a critical link in the DNS chain. A nameserver can be located anywhere including the registrar, your own server etc., you can even have multiple nameservers for backup but typically two are listed. As far CF goes unless you are on the enterprise or business plan you are required to use their nameservers if you want to utilize their proxy service. The nameserver is not a man in the middle service.John connor wrote: ↑Sat Mar 02, 2019 2:09 amIt is as I say it is. They are a "middle man." When you make a request to your domain, it hits your domain register first. Then from there it's routed to CloudFlare and then CloudFlare contacts your host.
I say man in the middle because they are a reverse proxy. They stand in the middle of your host and domain provider.
Users browsing this forum: No registered users and 13 guests