On Thu, 25 Aug 2005, Brad Knowles <[EMAIL PROTECTED]> wrote:
The real solution for this problem is to use a database back-end,
and have monitoring data update the database information in near
real-time. You could also distribute that database information from
the "master" server to the "slaves" via standard database techniques.
You might be able to put something together with BIND and the
DLZ-BIND stuff, but I think you're probably better off with something
like PowerDNS.
I haven't looked hard at PowerDNS, but one of the advantages of
BIND-DLZ is that
it is pretty damn flexible about the database schema and queries used. But for
Adrian's desire to keep the whole thing running on any standard dns kit, I've
long thought that something like BIND-DLZ would offer advantages. I currently
use it to run three nameservers, with a MySQL backend distributed using
MySQL's
own replication. I don't have a particularly high load, but it has worked like
a charm for me so far. It is said that there are improvements to be gained by
using the BDBHPT driver, possibly still using MySQL to store and replicate the
data and then pulling it into BDBHPT locally, but I haven't found a need to
experiment with this yet.
It seems to me the main advantage here would be that a given nameserver could
return a different set of results for each query, thereby hopefully
evening out
the spikes a bit. I don't know how random an ORDER BY RAND() really is, but it
would be worth looking at. In fact, Ask, if you could let me have something a
kin to a copy of the current database I don't mind doing a bit of
experimenting
with this.
--
Chris Hastie
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
