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
That's what I'm doing now. Minimal TTL with Cloudflare is 120.
Then use something different you need low about the same as your doing checks. If you checking every minute then ttl needs to be 60
I appreciate you're comments @nitro.
I should make it clear that this whole thing is an experiment. I'm simply exploring what's possible on a showstring budget.
I think latency does make a difference, at least on a large scale. Sending a European visitor to Texas makes a different browsing experience than if he/she was served from a European location. That's my first priority -- optimizing the visitor browsing experience by serving them from the closest mirror.
HA is of course important. But it's a different thing than geolocation. I've got HA now I think, but at the expense of geolocation when a mirror goes down. That's unavoidable, unless I deploy more than one server in each region.
Well, in that case I would move the US West Coast service to Japan and scale it up as necessary to handle the traffic, and scale down the France server.
That a good point, and is part of the reason I started doing geolocation by continent, as it's somewhat easier to map out traffic routes.
Yes I know. But at the moment all of this is kind of "proof of concept", so the difference between 120 and 60 is irrelevant I think. Not to mention that ISP caching nameservers may well ignore anything below 3600-7200 entirely
Thats why I force my NS to 8.8.8.8 will have a lok into this tuesday night+ have exam 1PM tues
But we can't do that for eveyone in the world
Well, there is the PAYG plan, "€1 per million requests plus €1 per zone monthly with free usage tier of 250 000 requests per month per domain".
Then, it's free up to 250K, which I think is small (depending on your TTLs and traffic).
Yep. Its true. We just need to force the world into 8.8.8.8
That's what I mean. It's minimal €1 -- for the zone with 250 000 requests per month. That nearly doubles my budget. I can have three or four more mirrors for that kind of money
Nearly there I think. I just did ...
So the US East mirror (nc.kate-cms.com, North Carolina) is offiline.
Monitoring script picked it and: removed its A record for kate-cms.com; changed the A record for nc.kate-cms.com to another available mirror (NL).
If you're in the East US and browse to kate-cms.com you're taken to NL as the failover.
If you try to browse directly to nc.kate-cms.com from anywhere you land at NL.
Then they should have changed the schema, because I have a free account o_O
Hmmm. I think case I think there could be better alts than NL?
Depends where you are. For me, NL is just ~ 10 ms slower than North Carolina
The logic for assigning a fallback needs to be refined, absolutely. And how it's done will depend on the alternates available.
But for now, the important things (for me) is that a fallback is successfuly assigned, and it works for browsing.
BTW, I'd be interested to hear from anyone regarding the little geolocation test at:
http://kate-cms.com/geolocation-test/
(Is info display, or do you get failed message?)
Looks correct -
Don't want to share my location, but the lat-long is just a few blocks off.
Distances from you to our site mirrors:
When you're setting your TTL for DNS so low remember it will do a dns lookup each time as well, you're just slowing down things more this way I think...
Good point. It's a balancing act. Maybe as long as TTL is larger than the average visitor time on site the impact would be minimal...
But if the TTL is larger than the average visitor time and the visitors current node breaks it's no use for that current visitor. Unless you expect every visitor to keep refreshing untill the TTL expires.
Well. Depends. AS anycast dns increases speed. Plus its only a few kb
That's why I said it's a balancing act.... I think there's too many variables to be 100% certain: there's the browser's cache (different from browser to browser), the OS cache (also different) and the ISP's cache. I don't see it possible to build anything that's 100% predictable with DNS.
There's a nice statistical probability exercise there for someone... Given X visitors per day, an average visitor duration of Y minutes, a TTL of 2 minutes and a server uptime average of 99%, what is the probability of a visitor getting a 'server unavailable' message?
Hello,
With reference to http://www.gslb.me we provide geolocation and HA/failover at the same time. Let us know at [email protected] if you need help setting up complex DNS resolution rules.
Welcome to LET
If I understand your website correctly, you'll do geolocation/failover for one domain with two targets (mirrors) for free, right?
Part II -- monitoring & Cloudflare DNS changes.
http://kate-cms.com/geolocation-with-php-part-ii/
@sleddog your solution makes browsing your website blazing fast even from the arse of the world ( Argentina)!
Ha
Which mirror did you get?
Hello,
That's correct: our free plan includes several other things such as customizable health checks, a set of different geo-routing algorithms and DNS firewall capabilities.
We are in the process of releasing an analytics set of features for full reporting on DNS traffic/resolution to keep track of who is resolving your FQDNs
Us east I believe
Edit: you are doug from Canada who had a camera that showed snowy weather?
Yup, even in May, though it's mostly gone now