eebcd66a92339b719c723c770b808fe0389eecfe
Hierarchical-DNS.md
... | ... | @@ -25,13 +25,11 @@ For all of these servers they have a specific IP assigned, are not anycasted, on |
25 | 25 | |
26 | 26 | **{{name}}.root-servers.dn42** - This server is authoritative for "." (dot) only. |
27 | 27 | |
28 | -**{{name}}.dn42-servers.dn42** - This server is authoritative for "dn42" only. This would be where the records for all forward dns nameservers would be. Similar to our current root setup. |
|
28 | +**{{name}}.zone-servers.dn42** - This server is authoritative for "dn42" only. This would be where the records for all forward dns nameservers would be. Similar to our current root setup. |
|
29 | 29 | |
30 | 30 | **{{name}}.in-addr-servers.arpa** - This server is authoritative for "arpa", "in-addr", and each of the 172 zones for dn42 ip space. For non dn42 ip space NS records to the respective darknet would need to be registered. |
31 | 31 | |
32 | -**{{name}}.zone-servers.arpa** - This server is authoritative for any RFC 2317 delegations. When generating for the rdns zones if nameservers are registered for a /25-28 inetnum the NS should point here to allow for proper delegation. |
|
33 | - |
|
34 | -**{{name}}.zone-servers.dn42** - This server holds the zone files for the various *-servers.* |
|
32 | +**{{name}}.dn42-servers.arpa** - This server is authoritative for any RFC 2317 delegations. When generating for the rdns zones if nameservers are registered for a /25-28 inetnum the NS should point here to allow for proper delegation. |
|
35 | 33 | |
36 | 34 | ## Example DNS setup |
37 | 35 |