So, if at any time someone has malicious intentions by carrying out jingling attacks or bot visitors on your blog, then one solution to protect your blog is to use a cloudflare service. Check out reviews about cloudflare and how to set it up for use on blogger.
What is Cloudflare?
Cloudflare is a server site for internet services in the form of Content delivery network (CDN) which refers to a group of geographically distributed servers that work together to provide fast delivery of Internet content.
For blogspot/blogger users, cloudflare services will certainly be very useful in the stage of switching from blogspot sub domains to top level domains, such as .com, .net, .org, .my.id, .web.id, .eu.org and so on.
Why Use Cloudflare ?
For those of you who are still confused about the usefulness of cloudflare services, here are some reasons why using cloudflare services in terms of changing from a blogspot sub domain to a top level domain.
The custom domain configuration on the blogger page cannot be saved or blogger cannot recognize the DNS of the custom domain name you are using. This problem lies in the custom domain that you have not registered or cannot be registered with the default standard domain nameserver from the domain name service provider where you bought the domain name.
One solution so that your domain name can be integrated with the nameservers is to use DNS (domain name server) from the free cloudflare service without a time limit.
The cloudflare service has good protection from Jingling attacks and Visitor Bots. For blogger users of course this will be very helpful to be able to keep their blog safe and stable.
While the benefits of using a CDN vary depending on the size and needs of the Internet properties, the main benefit for most users can be broken down into 4 distinct components:
- Increase website load time – By distributing content closer to website visitors by using a nearby CDN server (among other optimizations), visitors experience faster page load times. Since visitors are more likely to click from sites that load slowly, CDNs can reduce bounce rates and increase the amount of time people spend on sites. In other words, a faster website means more visitors will stay and stay longer.
- Reduced bandwidth costs – The cost of bandwidth consumption for website hosting is a major expense for websites. Through caching and other optimizations, a CDN can reduce the amount of data the origin server has to provide, thereby reducing hosting costs for website owners.
- Improved content availability and redundancy – A large amount of traffic or hardware failure can interfere with normal website functionality. Thanks to its distributed nature, CDNs can handle more traffic and withstand hardware failures better than many origin servers.
- Improve website security – CDNs can improve security by providing DDoS mitigation, security certificate upgrades, and other optimizations.
How do CDNs work?
At its core, a CDN is a network of servers linked together with the goal of delivering content as quickly, cheaply, reliably and securely as possible. To increase speed and connectivity, CDN will place servers at the point of exchange between different networks.
These Internet Exchange Points (IXPs) are the primary locations where different Internet providers connect to give each other access to traffic coming from their different networks. By having connections to these high-speed, highly interconnected locations, CDN providers can reduce the costs and transit time of high-speed data delivery.
In addition to server deployment on IXP, CDN makes a number of optimizations to standard client/server data transfers. CDN locates Data Centers in strategic locations around the world, enhances security, and is designed to withstand various types of Internet failures and bottlenecks.
Content Network Engineering
The Internet is designed according to the principles end to end. This principle keeps the core network relatively simple and transfers as much intelligence as possible to the network endpoints: hosts and clients. As a result, the core network is specialized, simplified, and optimized only for forwarding data packets.
Content Delivery Networks augment end-to-end transport networks by distributing intelligent applications using techniques designed to optimize content delivery. Integrated overlays generated using web caching, server load balancing, request routing, and content services.
The web cache stores popular content on the servers that have the greatest demand for the requested content. These shared network tools reduce bandwidth requirements, reduce server load, and increase client response times for cached content. The web cache is populated on request from the user (pull caching) or based on preloaded content propagated from the content server (push caching).
Server load balancing uses one or more techniques including service-based (global load balancing) or hardware-based (i.e. layer 4–7 switches, also known as web switches, content switches, or multilayer switches) to share traffic among a number of servers or web cache. Here the switch is assigned one virtual IP address. Traffic arriving at the switch is then routed to one of the real web servers connected to the switch. This has the advantage of balancing load, increasing total capacity, increasing scalability, and providing increased reliability by redistributing failed web server loads and providing server health checks.
Content clusters or service nodes can be formed using layer 4-7 switches to balance load across multiple servers or multiple web caches in the network.
Request routing directs client requests to the content source that is best able to serve the request. This may involve directing client requests to the service node closest to the client, or to the one with the most capacity. Various algorithms are used to route requests. This includes Global Server Load Balancing, DNS based query routing, Dynamic metafile generation, HTML rewriting, and any transmission. Proximity—selecting the closest service node—is estimated using a variety of techniques including reactive probing, proactive probing, and connection monitoring.
CDNs use a variety of content delivery methods including, but not limited to, manual asset copying, active web caching, and global hardware load balancing.
How to Configure Cloudflare
An easy guide in configuring a custom blogspot domain using the cloudflare service, to get started make sure you have registered and have activated your cloudflare account via email confirmation.
- The first step is to login to the cloudflare account that you have created.
- If you have logged in, then please select the menu Home and click Add website to add a domain that you have.
- Type the domain name that you will use on blogspot after that click Add site and click Next.
- Choose a plan Free if you want to use the free cloudflare service then continue click Confirm Plan.
- In this step you will see the standard DNS settings for the domain and hosting server. Okay, you just delete all the standard settings so it’s not confusing, later you will replace the DNS settings with the settings for your domain. Please delete everything by clicking the icon cross. The method can be seen in the image below.
- After all the standard settings have been removed, then you enter the DNS settings for your domain one by one. The method can be seen in the image below. Enter blogger CNAME and blogger IP, to find out the CNAME name of your blog, please enter the blogger dashboard then select menu Settings >> select Base or scroll down to settings for Custom domain >> click and enter Domain Name then press the button save which will display the CNAME name for the blog that will use the custom domain.
As for the following Blogger IP:
Name Type TTL R-DATA @ A 14400 216,239.32.21 @ A 14400 216,239.34.21 @ A 14400 216,239.36.21 @ A 14400 216,239.38.21 www CNAME 14400 ghs.google.com Unique Hosts CNAME 14400 Unique Records
Please save the data if you need it again at any time because the data will only appear once. However, if you forget to save your blog’s CNAME data and you want to know the CNAME name for your blog, please open the codeflare article on How to Install a Custom Domain (my.id) for Blogspot to be able to find out your blog’s CNAME data again.
- Continue now enter all DNS records as shown in the image below. Note that for the second DNS CNAME record, the data must be entered with the CNAME and RDATA records from your blog data that you recorded earlier. When you’re done, click the button Continue.
- In this step you will get a DNS nameserver which will later be entered into the nameservers in the domain settings where you bought the domain name. Remember ! record or save the nameserver data first. Next you need to go to the site where you bought the domain name then go to the domain settings page and change your domain registrar’s default nameserver to the nameservers from cloudfalre. After completing the nameserver update, please wait for 1×24 hour propagation so that the domain name can be fully functional. Usually, the fastest 1 hour of domain propagation is complete and the domain name can function properly.
- After the propagation is complete, please check whether your domain name can display the content of your blog. If you have, don’t forget to activate the tick Redirect to www and disable the https check first so that there is no crash on ssl (https) then after a few seconds re-enable the https check.
- Congratulations, the configuration for changing the blogspot domain has been completed and now the blogspot website can be accessed using a custom domain.
How to Set a Blogger Custom Domain Using Cloudflare, How to Connect a Domain to Blogspot Using Cloudflare, How to Change a Blogspot Domain to a Custom Domain .com .net .org .id .my.id .web.id .us .co.id .ac.id . Gov. From the Cloudflare Client Area Menu, How to Install Cloudflare Free SSL on Blogger