bind9-tutorial | use bind9 to setup your own DNS server
kandi X-RAY | bind9-tutorial Summary
kandi X-RAY | bind9-tutorial Summary
bind9-tutorial is a Shell library. bind9-tutorial has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
This repository provides and outline on how to setup a dns server using docker. Basic knowledge about dns records and network masks is assumed. A basic setup is provided to allow machines inside of a network to set their own dns records. Authentication to the dns server is not setup, however this can be restricted via using a key or restricted using an ip address. If you are interested in learning more about the configuration syntax, documentation is available at this link.
This repository provides and outline on how to setup a dns server using docker. Basic knowledge about dns records and network masks is assumed. A basic setup is provided to allow machines inside of a network to set their own dns records. Authentication to the dns server is not setup, however this can be restricted via using a key or restricted using an ip address. If you are interested in learning more about the configuration syntax, documentation is available at this link.
Support
Quality
Security
License
Reuse
Support
bind9-tutorial has a low active ecosystem.
It has 0 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
bind9-tutorial has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of bind9-tutorial is current.
Quality
bind9-tutorial has no bugs reported.
Security
bind9-tutorial has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
bind9-tutorial does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
bind9-tutorial releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of bind9-tutorial
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of bind9-tutorial
bind9-tutorial Key Features
No Key Features are available at this moment for bind9-tutorial.
bind9-tutorial Examples and Code Snippets
No Code Snippets are available at this moment for bind9-tutorial.
Community Discussions
No Community Discussions are available at this moment for bind9-tutorial.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install bind9-tutorial
This repository assumes that you are looking to setup a home network called home.int which has an acl set to a private network of 172.16.0.0/12 via the home acl defined in ./etc/bind/named.conf feel free to change this subnet to match the ip address range of your home network.
Run the create-rndc-key.sh script to generate a rndc.key file. Delete the options block if necessary in the generated ./etc/bind/rndc.key file. An example of what the file should look like is provided below:
Modify the ./etc/bind/named.conf file to update the CIDR mask to suit the ip range of the network. This allows machines on your network to set their own dns records.
(optional) update the ./etc/bind/named.conf.options file to point to the upstream dns servers of your choice.
(optional) update the ./var/lib/bind/home.int.hosts replacing my-machine with the name of the machine in the domain and optionally adding an e-mail address in the SOA.
When you are ready to run the docker image, run the set-bind.sh script to update the file permissions of the etc and var directories to user 101 as this is expected user id needed to allow bind to read the files.
copy the docker-compose-example.yml file to docker-compose.yml and update the ip address of the host that will run the bind9 server. I've left in an example value of 172.16.81.120 which you can modify to suit your needs.
run docker-compose up -d to start the bind9 container.
update the ./scripts/update-record-example to point to the correct dns server and set the ip address of some A record and run nsupdate ./scripts/update-record-example to update the record.
To test that dns record has been set you can run host test.home.int 172.16.81.120 (replace 172.16.81.120 with your ip address) to verify that the record has been set.
Run the create-rndc-key.sh script to generate a rndc.key file. Delete the options block if necessary in the generated ./etc/bind/rndc.key file. An example of what the file should look like is provided below:
Modify the ./etc/bind/named.conf file to update the CIDR mask to suit the ip range of the network. This allows machines on your network to set their own dns records.
(optional) update the ./etc/bind/named.conf.options file to point to the upstream dns servers of your choice.
(optional) update the ./var/lib/bind/home.int.hosts replacing my-machine with the name of the machine in the domain and optionally adding an e-mail address in the SOA.
When you are ready to run the docker image, run the set-bind.sh script to update the file permissions of the etc and var directories to user 101 as this is expected user id needed to allow bind to read the files.
copy the docker-compose-example.yml file to docker-compose.yml and update the ip address of the host that will run the bind9 server. I've left in an example value of 172.16.81.120 which you can modify to suit your needs.
run docker-compose up -d to start the bind9 container.
update the ./scripts/update-record-example to point to the correct dns server and set the ip address of some A record and run nsupdate ./scripts/update-record-example to update the record.
To test that dns record has been set you can run host test.home.int 172.16.81.120 (replace 172.16.81.120 with your ip address) to verify that the record has been set.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
