[luv-main] DDNS Server [Scanned]
Hi All, I'm looking for a DDNS package that I can setup on a CentOS 5 server for potentially thousands of devices deployed at thousands of sites world wide. I have had a quick look at Bind9, which I think may buckle under this load if deployed by itself. I have also looked gnudip, but would like some feedback on how easy it is to setup and maintain, also any other packages people have used. TIA, Chris -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
Christopher M. Bailey wrote:
Hi All,
I'm looking for a DDNS package that I can setup on a CentOS 5 server for potentially thousands of devices deployed at thousands of sites world wide. I have had a quick look at Bind9, which I think may buckle under this load if deployed by itself. I have also looked gnudip, but would like some feedback on how easy it is to setup and maintain, also any other packages people have used.
Normally dynamic DNS works something like this: curl http://dyndns.org/update.cgi -F domain=foo.example.net -F password=UNPRINTABLE -F address=1.2.3.4 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.
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.
http://etbe.coker.com.au/2010/12/08/dynamic-dns/ The above URL describes how I got dynamic updates working with BIND. It isn't that hard to do and while the method I use to prevent clients from modifying the main zone could get ugly with thousands of mutually untrusted clients it wouldn't be that difficult to script. I can't imagine why BIND would have any peformance problems with this. If 3000 clients do an update every hour then it would be an average load less than one request per second and probably most peaks would be less than 10 per second. That is nothing given that nice AMD64 systems are being discarded nowadays. -- My blog http://etbe.coker.com.au Sent from an Xperia X10 Android phone
participants (4)
-
Christopher M. Bailey -
Jason White -
Russell Coker -
Trent W. Buck