Ross, I will contact one of the developers to get the CLI import functions documented. My initial take on this is that the backend has a lot of code that was custom written for import work for specific customers. It was left in the code base for future generalization.
If I recall correctly there is a way to import a whole dir of standard BIND9 generated db files (like a slave would have), but the names of the db files have to be converted usually to use the unxsBind format. This format is the tZone.cZone, e.g. yourdomain.com would have a db file called simply "yourdomain.com." (Was developed and worked fine with more than a 1000 zone file import for a major UK and European DNS provider that uses unxsBind and has used it for the past 4 years. A major corporate supporter of our FOSS projects.) The other import related functions are related to associating zones with end users and other related tables like registrars and ip blocks (used for controlling PTR record permissions on shared zones like the in-addr.arpa zones. Cheers! Dylan -- AM Support Staff Unixservice, LLC. +1 310-356-6265 +1 630-206-9449 http://unixservice.com 155 S.E. 16th Ave Portland, Oregon 97214 USA No binding contract will be made between an employee of Unixservice and a third party either verbally or by email, until a written document has been signed on behalf of Unixservice. This e-mail is intended only for the use of the addressees named above and may be confidential. If you are not an addressee you must not use any information contained in nor copy it nor inform any person other than the addressees of its existence or contents. _______________________________________________ unxsBind mailing list [email protected] https://lists.openisp.net/mailman/listinfo/unxsbind
