add missing documentation

Signed-off-by: Marek Küthe <m.k@mk16.de>
This commit is contained in:
Marek Küthe 2023-01-01 19:27:39 +01:00
parent c1a79053f4
commit 79f6927ae8
No known key found for this signature in database
GPG Key ID: 7E869146699108C7
4 changed files with 63 additions and 5 deletions

View File

@ -1,7 +1,5 @@
# Servers
HINT: This is currently a work in progress by @mark22k
## Recursive
| DNS | IP address |

View File

@ -5,6 +5,8 @@ Note: This documentation is in WIP.
In entitydb, the persons or organizations are registered in CRXN with their IP addresses. Here, each entity has a JSON file in which the data is recorded. The entitydb is also abbreviated as edb.
[entitydb](https://codeberg.org/CRXN/entitydb/)
- [Format and Rules](format-rules)
Attributes:

View File

@ -1,5 +1,27 @@
# DNS
TODO: Add documentation @mark22k
In the `radv` protocol in bird, there is a possibility to pass DNS servers to the clients. This requires a working recursive DNS server. If you only want to resolve CRXN domains, you can use a DNS server from [Additional/DNS](../additional/dns). If you also want to resolve Clearnet domains, it is recommended to use your own DNS resolver (recursive or forward) like Coredns or Unbound.
You can take look at [Additional/DNS](../additional/dns) in the meantime.
With the following option, you can specify a DNS server:
```
rdnss fd92:58b6:2b2::5353;
```
The following option allows you to specify multiple DNS servers:
```
rdnss {
ns fd92:58b6:2b2::5353;
ns fd92:58b6:2b2::5354;
};
```
If you also have a CRXN domain, you can also tell the clients a search domain:
```
dnssl "home.example.crxn";
```
```
dnssl {
domain "home.example.crxn";
domain "lab.home.example.crxn";
};
```

View File

@ -39,7 +39,43 @@ You can advertise a default route, to `fd00::/8` or simply all routes in your ro
### Advertising a single `fd00::/8`
TODO: Add this as I normally don't do this even though one should as it means less memory consumption and advertisement updates
In order not to have the default route in our normal routing table, it is recommended to make an extra routing table for the radv routes. There we define the default route.
```
ipv6 table radv_routes;
protocol static {
ipv6 {
table radv_routes;
export all;
};
route fd00::/8 unreachable;
}
protocol radv
{
# Enable propagating of routes exported to us via radv to hosts
propagate routes yes;
ipv6 {
# Export ula default routes into the radv advertisement
export all;
table radv_routes;
};
# Interface to run radv on - only eth0 (change to what you want)
interface "eth0" {
# Advertise your prefix
prefix fd40:ec65:5b4c::/64 {
# Defaults are fine
};
# Prevent advertising of default route
default lifetime 0;
};
}
```
### Advertising all known routes