dn42/wiki
1
Fork 0
mirror of https://git.dn42.dev/wiki/wiki.git synced 2025-02-24 18:35:54 +01:00
Code Releases Activity

Updated Hierarchical DNS (markdown)

Browse Source
This commit is contained in:
siska 2015-06-05 08:35:29 +02:00
parent 2136f9955a
commit eebcd66a92
1 changed files with 2 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Hierarchical-DNS.md
View File

@ -25,13 +25,11 @@ For all of these servers they have a specific IP assigned, are not anycasted, on
**{{name}}.root-servers.dn42** - This server is authoritative for "." (dot) only.
**{{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.
**{{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.
**{{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.
**{{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.
**{{name}}.zone-servers.dn42** - This server holds the zone files for the various *-servers.*
**{{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.
## Example DNS setup