diff options
author | rexxnor <rexxnor+gnunet@brief.li> | 2019-01-25 17:24:47 +0100 |
---|---|---|
committer | rexxnor <rexxnor+gnunet@brief.li> | 2019-01-25 17:27:29 +0100 |
commit | 8b48d928864af10bd1a31e55daf23c54bf0e4100 (patch) | |
tree | ceac0ea2a7ce38a2d6947aac67b501e58bf46e7f /doc/handbook/chapters/developer.texi | |
parent | d91f5dcc352b6116e346c2a45edfd72ed4de3f9a (diff) | |
download | gnunet-8b48d928864af10bd1a31e55daf23c54bf0e4100.tar.gz gnunet-8b48d928864af10bd1a31e55daf23c54bf0e4100.zip |
fixed up documentation for ascension
Diffstat (limited to 'doc/handbook/chapters/developer.texi')
-rw-r--r-- | doc/handbook/chapters/developer.texi | 16 |
1 files changed, 6 insertions, 10 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi index 1d3e1d3fb..2da262b34 100644 --- a/doc/handbook/chapters/developer.texi +++ b/doc/handbook/chapters/developer.texi | |||
@@ -8130,19 +8130,15 @@ The transformation of MX records is done in a simple way. | |||
8130 | gnunet-namestore -z example.com -n mail -R 3600 MX n 10,mail | 8130 | gnunet-namestore -z example.com -n mail -R 3600 MX n 10,mail |
8131 | @end example | 8131 | @end example |
8132 | 8132 | ||
8133 | Finally, one of the biggest struggling points was the NS records that are found | 8133 | Finally, one of the biggest struggling points were the NS records that are found |
8134 | in top level domain zones. The intended behaviour for those is to add GNS2DNS | 8134 | in top level domain zones. The intended behaviour for those is to add GNS2DNS |
8135 | records for the zone so that gnunet-gns can resolve the for those domain on it's | 8135 | records for those so that gnunet-gns can resolve records for those domains on |
8136 | own. Also a very important aspect of this is, that gnunet needs to be able to | 8136 | its own. This requires migration of the DNS GLUE records as well, provided that |
8137 | resolve the nameservers from it's own database. This requires migration of the | 8137 | they are within the same zone. |
8138 | DNS GLUE records as well. | ||
8139 | 8138 | ||
8140 | This proved to be quite a challenge to implement, as in GNS every dot is a | 8139 | A solution was found by creating a hierarchical zone structure in GNS and linking |
8141 | strict zone cut. | ||
8142 | |||
8143 | The issue was fixed by creating a hierarchical zone structure in GNS and linking | ||
8144 | the zones using PKEY records to one another. This allows the resolution of the | 8140 | the zones using PKEY records to one another. This allows the resolution of the |
8145 | nameservers to work within GNS. | 8141 | nameservers to work within GNS while not taking control over unwanted zones. |
8146 | 8142 | ||
8147 | @node DNS Zone Size | 8143 | @node DNS Zone Size |
8148 | @subsubsection DNS Zone Size | 8144 | @subsubsection DNS Zone Size |