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-08 04:57:49 +02:00
parent 5444112615
commit bb81318b27
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Hierarchical-DNS.md
View File

@ -23,9 +23,9 @@ Note: With this system it could be possible to merge the IANA root file.. but it
For all of these servers they have a specific IP assigned, only respond to their authoritative zones, and do not allow recursion. For all of these servers they have a specific IP assigned, only respond to their authoritative zones, and do not allow recursion.
**{{name}}.root-servers.dn42** - This server is authoritative for "." (dot) only. **{{name}}.root-servers.dn42** - This server is authoritative for "." (root zone).
**{{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}}.zone-servers.dn42** - This server is authoritative for "dn42", "hack", .. 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}}.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.