Custom Query (15 matches)

I can't quite imagine a real situation you would really want to make sure an IP does not have rDNS, but it should be supportable. We need a pattern tag to indicate this case. It should iterate the same as any other template record, so that eg:

10.0.0.0/28 A+PTR %i.foobar.com 10.0.0.8/29 A+PTR <new tag> 10.0.0.12/30 A+PTR lil-%4.foobar.com

produces:

=10-0-0-0.foobar.com:10.0.0.0:ttl::: =10-0-0-1.foobar.com:10.0.0.1:ttl::: =10-0-0-2.foobar.com:10.0.0.2:ttl::: =10-0-0-3.foobar.com:10.0.0.3:ttl::: =10-0-0-4.foobar.com:10.0.0.4:ttl::: =10-0-0-5.foobar.com:10.0.0.5:ttl::: =10-0-0-6.foobar.com:10.0.0.6:ttl::: =10-0-0-7.foobar.com:10.0.0.7:ttl::: =lil-12.foobar.com:10.0.0.12:ttl::: =lil-13.foobar.com:10.0.0.13:ttl::: =lil-14.foobar.com:10.0.0.14:ttl::: =lil-15.foobar.com:10.0.0.15:ttl:::

(blanking rDNS entries for .8 through .11)

RPC support was stubbed out and partially filled in as of r123, but has only had a handful of cosmetic fixes and labelling tweaks. It needs to be updated to match the updates to the core library, and thought given to exposing more subs.

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