Page History

...

There are three components to the upload process:

1) The named.conf

...

configuration file tied to the zones you are uploading

...

(required)

This tells the importer the Zone Name and where the zone file is written. It could be as simple as a multi-line file:

...

zone "my-zone.com" { type master; file "/usr/local/zones/my-zone.com.zone"; };
zone "my-other-zone.com" { type master; file "/usr/local/zones/more/my-other-zone.com.zone"; };
zone "my-third-zone.com" { type master; file "/usr/local/zones/more/even more/my-third-zone.com.zone"; };

For a sample Simple Config conf.conf

2) A ZIP or TAR file of the DNS zones themselves (required)

This is as it sounds - a file archive where we can find the zones and it should match the configuration file uploaded in Step 1.

For a sample ZIP zones.zip

3) Match CSV for assigning DNS Zones to Resources (optional)

This file allows the administrator to "assign" zone files to a given Resource. If you have Imported a group of Resources, they have Resource IDs associated with them. You can then import DNS zones and assign them to hose Resource IDs. When complete, you will be able to pull up the Resource Record and see the DNS Zones associated to that Resource ID.

my-zone.com,test-01,fun stuff
my-otherzone.com,test-02,great stuff
even-reverse-zones.arpa,test-03,amazing stuff

Note the columns are the Zone Name, the Resource ID, and Notes.

For a sample CSV config.csv