>> It has at least one problem: all names will be lost when you create >> a "self" >> host in server-manager.
> I haven't looked at the code, but this implies that the hosts > are not being entered into the hosts database, so the system doesn't > really know about them. It uses a feature of dhcp3 that sends dynamic updates to bind. > Having two A records > (one a real name and one pc-xxxx) isn't harmful, as long as the PTR > records point to the name you really want to use. Agreed. Shortly before releasing the solution based on dhcp3 and bind I used a different approach that, through a cron script checked dhcpd.leases to see if a new ip had been assigned (using mtime and parsing the whole file) and signalled bind (dyn upd). This solution could be easily modified to adapt nicely to SME hosts db, but it will be a bit heavy on cpu* and will suffer from a small delay (up to a minute). * bind reload for every assigned ip and parsing of dhcpd.leases, usually long, because a static ip assignment through server-manager panel is the suggested way to have ip mappings when pc count is low). cron could be avoided "daemonizing" the script. I think that the best thing to do would be to make SME fiddle only with ip it knows, leaving the other to bind and dynamic update. It would mean that all ip in the dhcp range should not be dealt with in bind templates. Ciao, Filippo -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
