This dns server will only be useful to publish your ip addresses, it can not be used as a cache.
Requirements:
make tinydns-data and copying it to
PATH should suffice.
dns
At /home/dns create the file
data.
Put the dns configuration in this file.
The spcification of the configuration format
can be found on the
tinydns-data
page.
More general information and tutorials
can be found on the
djbdns
page.
Whenever /home/dns/data is changed,
change the working directory to
/home/dns and run
tinydns-data.
Create the following longrun
source directory
in the src/web/shibari-udp-ip4-srv
subdirectory of the
system configuration directory.
shibari-udp-ipv4-srv ├── dependencies.d │ ├── mount # empty/arbitrary │ └── networking # empty/arbitrary ├── notification-fd # 3 ├── producer-for # shibari-udp-ipv4-log ├── run # see below └── type # longrun
with the following run script:
#!/bin/execlineb -P fdmove -c 2 1 s6-envuidgid dns shibari-server-udp -U -d3 -f /home/dns/data.cdb @YOURIP@
Replace @YOURIP@
with the ip address of the server.
If desired repeat the process for IPv6,
the directory would then be
system/src/web/shibari-udp-ip6-srv
and producer-for
should contain shibari-udp-ip6-log.
Create the following longrun
source directory
in the src/web/shibari-tcp-ip4-srv
subdirectory of the
system supervision tree.
shibari-tcp-ipv4-srv ├── dependencies.d │ ├── mount # empty/arbitrary │ └── networking # empty/arbitrary ├── notification-fd # 3 ├── producer-for # shibari-tcp-ipv4-log ├── run # see below └── type # longrun
with the following run script:
#!/bin/execlineb -P fdmove -c 2 1 s6-envuidgid dns fdmove 1 3 s6-tcpserver -1 -U -- @YOURIP@ 53 shibari-server-tcp -f /home/dns/data.cdb
Replace @YOURIP@
with the ip address of the server.
If desired repeat the process for IPv6,
the directory would then be
system/src/web/shibari-tcp-ip6-srv
and producer-for
should contain shibari-tcp-ip6-log.