Re: random host

--- shimi <shimi@shimi.net> wrote: > > DNS cache of the a record in a zone can be set differently than the rest > of the zone. So you can basically do that clients will check the hostname > again > and again, even every 20 seconds if you want. > > The way to do it is quite simple: > > random 10m IN A 1.2.3.4 > random 10m IN A 4.3.2.1 > > etc... and that way every time the site is accessed, the hostname is > re-checked... Setting very low DNS cache timeouts is bad. Who knows, php.net's might be able to handle it, but it's bad practice and severly frowned upon by any network adminstrator. I propose we set a static list of mirrors that would like to participate, ie primary mirrors. Each primary mirror could represent a broad geographical region, and be the best connected of that region (for instance, Europe, America, Asia, etc.). This would hugely offload the traffic from www.php.net, be easy to organize and maintain (only a handful of hosts to deal with), and provide the best service to the end-surfer (even if I'm in NY, a well connected Japaneese host is better than if I get redirected to any old host in Asia). This would be very easy and only involve a tad of planning. I run a primary mirror for mozdev.org and this is much the same way they're setup; only a couple primary mirrors, then secondaries for failover and specific geographic regions. H > > On Wed, 14 May 2003, Gabor Hojtsy wrote: > > > Hi! > > > > > an idea just popped into my head... random hosts. Would anyone see > anything > > > broken with random.php.net just taking a host to a random mirror which > is > > > not www? I'm thinking for apps that point to php.net (eg docref root) > etc, > > > as this would reduce some load on the server... when the country > redirect > > > stuff gets baked, and auto-redirect works, then it'll take the user to > their > > > closest mirror... > > > > Yep. I proposed adding my.php.net for this task earlier, but guys said > > we should reserve my.php.net for the Malaysia, and it is already > > registered for Malaysia. So I think this is a good idea. > > > > > thoughts? > > > sane ways of implementing it? :) > > > > The main consern about it is that we test hosts every hour. So we have > > info on whether the host was up the last hour or not. What if > > random.php.net redirects a user to a server which is down? > > > > About the implementation, I don't really know how to do it, but someone > > said DNS caches will be hard to overcome. This is not a huge problem for > > random mirrors, but for a "my mirror" it is... > > > > Goba > > > > -- > > Best regards, > Shimi > > > ---- > > "Outlook is a massive flaming horrid blatant security violation, which > also happens to be a mail reader." > > "Sure UNIX is user friendly; it's just picky about who its friends are." >