Differences
This shows you the differences between two versions of the page.
Next revisionBoth sides next revision | |||
opennic:srvzone [2017-04-19T02:01:22Z] – created jonaharagon | opennic:srvzone [2017-07-06T01:42:00Z] – fusl | ||
---|---|---|---|
Line 3: | Line 3: | ||
The information below is based on a Debian/ | The information below is based on a Debian/ | ||
- | Note that this configuration may be used for both Tier-1 and Tier-2 servers, as well as private servers. | + | Note that this configuration may be used for both [[tier1|Tier 1]] and [[tier2|Tier 2]] servers, as well as private servers. |
===== Getting the script ===== | ===== Getting the script ===== | ||
Line 14: | Line 14: | ||
chmod 700 srvzone | chmod 700 srvzone | ||
- | Now edit srvzone.conf with your preferred editor. You will see a section with paths for several files, which can be changed to match your configuration. The first three entries dictate where BIND will store the zone files. Note that file_master does not apply to Tier-2 servers. In the example paths given, note that $TLD will be expanded to each zone name as it is created -- so for example the string " | + | Now edit srvzone.conf with your preferred editor. You will see a section with paths for several files, which can be changed to match your configuration. The first three entries dictate where BIND will store the zone files. Note that file_master does not apply to Tier 2 servers. In the example paths given, note that $TLD will be expanded to each zone name as it is created -- so for example the string " |
Make sure the folder where you wish to store the files has been created. In the example srvzone.conf file, zones would be stored in / | Make sure the folder where you wish to store the files has been created. In the example srvzone.conf file, zones would be stored in / |