I've been looking into it.. The big problem here seems to be that the "no-ip -C" that asks questions and generates the binary config file actually talks to no-ip's server during the configuration and shows the domains associated with your user account.
I can think of a few ways for doing this: - Re-invent the wheel, reverse engineer noip2.c code to see how it stores data in no-ip.conf and how it interact's with the server to replicate it's behavior using debconf - Make some sort of more "static" debconf that would receive domains typed by the user and compare it with the domains that "no-ip -C" reads from the webserver, selecting those who match. - Creating some sort of patch for upstream or separate application allowing to command-line configure the daemon. Maybe we could even use noip2.c code for making a command-line configure utility facilitating this. Any thoughts? Ideas? -- Mário Meyer
