New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Do you really need anycast IP? Geo DNS is very different but cheaper
Whatever can georoute to the nearest server and work with cloudflare proxy basically is ideal. Cloudflare's "geosteering" seems to only be for super large businesses.
If you want Cloudflare proxy then Cloudflare load balancing is your only solution. Check this image https://pasteboard.co/rNjjmYZAcNH6.png
It is under Traffic > Load Balancing. Cost $15 per month
If DNS only then any geodns is ok. I am using Google Cloud DNS. Amazon Route 53 is popular choice too. They are pay as you go model so the cost is based on number of queries
I tried to search for more info and found this: https://cloud.google.com/blog/products/networking/dns-routing-policies-for-geo-location--weighted-round-robin
So, google cloud DNS does not have health check so you can't do a dns failover setup? Or is it already available now?
Why do you need cloudflare proxy? If you want all the bells and whistles that come with cloudflare, you probably should just pay for the load balancing feature. Looks like $5 per origin and $10 to enable the georouting. I wonder what counts as an origin though. I don't know if your two servers are counted as two origins, or if your many sites will each count as two origins. So 10 sites on 2 servers means you have 20 origins?
In any case, the fast and easy way is probably to use route53 georouting. If you wanted cloudflare proxy just to hide the IP, then you would need cloudfront. It's basically an aws cdn service, but it can be very expensive past the free 1 TB/month.
thanks somehow I missed that in cloudflare settings, i'll just use that
Yea i'll use cloudflare settings, i missed that, thanks for pointing it out
Because you mentioned you have sites, and not just one site, take note there's a limit of 20 origins on the basic cloudflare plan. Maybe 11 sites x 2 servers means 22 origins. But maybe they are reasonable and your two servers are just counted as 2 origins.
I've posted our Dedi offers here: https://lowendtalk.com/discussion/177451/new-dedicated-server-available-ryzen-5-5600g-intel-core-i7-6700k-starting-49-month#latest
There should be a server for you available
@NoComment yes. It doesn't failover so you will need their Load Balancer and the traffic cost is much more expensive than Cloudflare.
@apples2 I have just tested an interesting idea and it do work as expected.
I will use another domain domain_b.com at Google Cloud DNS and domain_a.com at Cloudflare. Domain_b is configured as geo routing so it will returm the nearest IP for each request. Domain_a.com is configured in Cloudflare as CNAME + Proxied with orange cloud.
When a user visits domain_a.com, Cloudflare will ask Google for the nearest IP and proxy the request.
With this configuration, I can minimize the cost at Google DNS by increasing the TTL so CF won't query too much. CF gives the free traffic and cache static files.
For fail over, I think multiple IPs per A record at Google Cloud DNS may works, CF may try multiple IPs before return an error. But I am not sure. May be it will fail. If you want CF proxy + health check then CF Load Balancing is the best choice
Cloudflare shares origins across multiple domains so he has 2 IPs = 2 origins. He can use those for multiple domains
;edit nevermind
what is your content policy? I can't find it. Like some providers allow adult porn and "hate speech" and conspiracy sites. Others don't.
@apples2 We don't have a specific content policy, if the content is legal and is not against the german law.
Thanks for the response
If something was legal in the USA but deemed to "hate speechy" for Germany, would you give me notice to take a single page down, or just shut off my entire service
@apples2 Our default procedure is to forward the abuse message. If you don't remove the site or the content and we will get those abuses again, we've to lock the server.
Considering people file abuse reports at will to take down anything they don't like, and Germany has some of the most restrictive speech laws, I think I'll pass.
Although your prices are really good and I recommend them to anyone not managing user generated content that may be controversial
Thank you
That's interesting, I have not thought of that. But your origin domain/ip will be public which might be a problem. A cost-effective and easy solution would be to only allow traffic from cloudflare IPs on the frontend server, since you are proxying with the cname. What do you think about this? Or is your primary use case for cloudflare the caching, and not a concern with ddos?
I have not tried this, but I think the most likely result is they try all the IPs round-robin.
That's quite reasonable. Can I ask why you are doing the cloudflare + google dns setup instead of just using cloudflare load balancing? Is it to save costs?
@NoComment I have 5 regions, us west east central + Netherlands + Singapore. All are promo cheap vps. The cost for Cloudflare Load Balancing is $30 per month (5 origins + geo). My main purpose is to save cost. If my website can make more than that then I rather use Cloudflare Load Balancing.
Currently, I set the TTL on GG cloud dns to 1 day so Cloudflare can cache dns better. If anything happens then I can easily change the record in Cloudflare to other backup IP or CNAME.
The cost is very small with this combination. Cloudflare is basically free. Cloud dns is $0.2 per zone and $0.7 per million queries. As I set TTL 1 day, I don't think that the queries will cost a few dollars.
My origin IPs are exposed through a completely random unrelated domain. I am sure no one will DDOS those IPs.
GeoDNS:
https://www.cloudns.net/geodns/ - Starts at $10
https://rage4.com/ - Starts at 20€
I found rage4 easier to setup and more performant, and at 20€ it has "unlimited" queries for a single domain and 78 records, so you could have 78 origins. Making it far cheaper than Cloudflare for big projects. But I found it very hard to navigate their UI to find how to cancel the plan after I was done with it.