Trent W. Buck <trentbuck@gmail.com> wrote:
Since you're talking about bind as a solution, I guess you're basically talking about implementing an alternative to dyndns.org (i.e. the hub) rather than a dyndns client (i.e. the spokes) ?
In that case, why are you talking about bind? You're not thinking of clients pushing updates to the hub via NOTIFY + IXFR, are you? Because I don't see how that could possibly work.
Bind could do it with dynamic updates: a script running on the Web server could run nsupdate for every request. I know nothing at all about the performance characteristics of such a solution, however. There might even be code in [insert favourite scripting language here] to perform the dynamic updates without running an external tool such as nsupdate.