devuan
/
nameserver
14
0
Fork 1
Code Issues Pull Requests Releases Wiki Activity
Setup of Devuan name server sub system.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
373 Commits
1 Branch
0 Tags
975 KiB
 
 
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Devuan Dev Team 6f79d0184b
Generated by DNS automation 		4 days ago
.gitignore initial capture 4 years ago
README.adoc Add instruction how to check for conflicts 2 years ago
dev-1.org.zone Add dev-1.org and dev-one.org 5 months ago
dev-one.org.zone Add dev-1.org and dev-one.org 5 months ago
dev1galaxy.org.zone added "a" to spf 6 months ago
devuan-slave.conf Add dev-1.org and dev-one.org 5 months ago
devuan.dev.zone LE autoupdate 2 weeks ago
devuan.net.zone Renumber to the new devuan.org ips; Remove unused NS 7 months ago
devuan.org.zone Add polpo 2 weeks ago
generate-rr.pl Add a check for empty mirrors_list.txt 2 years ago
generate-rr.sh Fix commits ownership 2 years ago
ip6arpa added usage comments 2 years ago
nsd.conf Add dev-1.org and dev-one.org 5 months ago
rr.devuan.org.zone Generated by DNS automation 4 days ago
zonediff.sh Include devuan-slave.conf in the diff 7 months ago

README.adoc

Nameservice Configurations

This directory contains configurations for the Devuan nameserver sub system. See also name service documentation.

Deployment of Configuration Changes

Changes to nameserver configurations should be done to this repository. Don’t forget to update the serial. Then: go to ns1:/etc/nsd/GIT, check out, run ./zonecheck.sh from /etc/nsd/GIT to verify that no changes in the runtime configuration will be overwritten and after merging the changes and commiting them back in git, copy up *.conf to .., and restart nsd.

This process is not automated yet, since configuration changes involve at least two levels of validation:

  1. it needs to be syntactically correct for the program(s) (nsd), and

  2. it needs to reflect the agreed upon intentions of "Devuan" as organisation.

The syntax checking can be done on the zone file(s), as it’s ordinary bind9 syntax. E.g. nsd-checkzone (of the nsd package) or named-checkzone (of the bind9utils package) may be used to confirm syntactic correctness.

The intentional correctness is of course rather a matter of the "sign-off" procedure is in use. Presently Devuan Caretakers have access to root@ns1 and can exercise the hands-on.