This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
irc:openbsd:nsd [2020/07/10 11:41] baytuch [Configuration check and start] |
irc:openbsd:nsd [2020/07/22 09:24] (current) baytuch |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| #notify: 193.201.116.2 NOKEY | #notify: 193.201.116.2 NOKEY | ||
| #provide-xfr: 193.201.116.2 NOKEY | #provide-xfr: 193.201.116.2 NOKEY | ||
| + | </code> | ||
| + | |||
| + | ====== Primary and secondary server ====== | ||
| + | If you need a secondary server to host the zone, you can do this as follows. Add to the block that describes your master zone, records about the secondary zone as in the example: | ||
| + | |||
| + | <code> | ||
| + | zone: | ||
| + | name: "example.net" | ||
| + | zonefile: "master/example.net.zone" | ||
| + | notify: 20.20.20.20 NOKEY | ||
| + | provide-xfr: 20.20.20.20 NOKEY | ||
| + | </code> | ||
| + | |||
| + | Create a new block in the secondary server config file, as in the example: | ||
| + | <code> | ||
| + | zone: | ||
| + | name: "example.net" | ||
| + | zonefile: "slave/example.net.zone" | ||
| + | allow-notify: 10.10.10.10 NOKEY | ||
| + | request-xfr: 10.10.10.10 NOKEY | ||
| </code> | </code> | ||