Custom Query (15 matches)

Instead of regenerating the entire on-disk data file straight from the database each time, export individual zones to separate files in a workspace, then concatenate them. Add a "modified" flag to the domain or revzone so we only have to walk through the details of zones that have been modified, and update those files - should give close to an order of magnitude or better speedup.

Observed on test copies of live data:

• 3081 local forward zones
• 2598 imported records from flatfiles in "main" zone
• 271 imported revzones from flatfiles
• 315 imported forward zones from autoaxfr flatfiles

Initial local forward zones only, ~43-65s Add all current flatfiles, ~114-160s

export_tiny doesn't handle many errors, so if it's passed a closed filehandle, the cache directory is variously missing, not a directory, or not read/writeable, or if there's some error creating and writing to the individual cache files, or the master file, it just keeps on going spitting warnings to stderr.

Code to date, primarily for reverse zones, sharply limits what records it will allow to be edited (or added).

Extend the validation layers to allow any syntactically valid record in any zone, and

Consider adding a configuration knob to keep the current behaviour ("strict"), the primary extension allowing import, export, and editing ("relaxed"), and a wide-open "anything syntactically valid" mode ("open").