An open source DNS Server Solution that includes a Web Management System, a Restful API, Dynamic DNS functionality, and a High Availability design. The web interface allows users to manage all DNS entry types, the adding and removal of their own domains, and a simple user control mechanism. DNS Server is horozontally scalable, thus if the load becomes to high simple depoloy additional slave DNS Servers. Dynamic DNS clients such as ddclient, DD-WRT, Tomato, are known to work with DNS Server. DNS Server is built on top of technologies such as Bind with DLZ Support, Tomcat 9.x, MariaDB(or MySQL 5.7+), NGINX, Ansible, and CentOS 7.x.
- Features
- Requirements
- Support
- Update API
- Installation Instructions
- Registra Nameserver Configuration
- Useful Links
- Donations
- License
- REST Based Update API based on the Dyndns2 protocol.
- Compatible with most DDNS clients.
- Fully functional web application for managment of hosts and user profile information.
- Designed for multiple slave DNS Servers.
- IPv4 DNS Record Updates.
- Basic user signup, forgot, and login functionlaity.
- Built on CentOS 7 with Bind 9.1x(compiled with DLZ support), Tomcat 9, and MaridbDB.
- Comming Soon - Many new DNS record types will be added. Ultimatly this will become a fully managed high availablity DNS server.
- Comming Soon - Ansible Deployment Scripts for Master and Slaves.
- Comming Soon - NGINX Slave Load Balanceing.
- Comming Soon - New User Authentication Methods. (FreeIPA?, LDAP?)
- At least 3 CentOS 7.* Virtual Machines or Servers.
- SSH Access to all DDNS Servers.
- If publically accessable, Port 53 (UDP) must be open from each slave DNS server to (and from) the internet.
Since I am extremely lazy I am not going to offer any support. Well maybe every once-n-a while. It really depends on my mood.
That being said, time was spent documenting each code section in the DNS Server. This should allow the scripts to be easily understood and modified if needed.
The update API was designed to mimic the dyndns2 protocol in order to make it compatible most DDNS clients. Once the Dynamic DNS Server is installed and running the API is avaialble. To access the API you will need credentials from the web application in order to use the API's Http Basic Authentication.
http://{username}:{password}@{yourdomain.tld or ip address}/ddns/update?&hostname={hostname}&myip={IP Address}
username [REQUIRED] Your Hiive.biz account username.
password [REQUIRED] Your Hiive.biz account password.
hostname [REQUIRED] Comma separated list of your Hiive.biz hostnames to update (up to 10 hostnames per request).
myip [Optional] The IP v4 Address that your Hiive.biz hostname(s) will be updated to. If no IP Address is specified the Hiive.biz system will attempt to obtain the IP Address.
good
IP Address for specified Hosts have been updated.
nochg
There is no update or change required. (No need to update more than once an hour without an IP change)
nohost
One or more Hosts are invalid.
numhost
More than the maximum of ten Hosts specified.
badaddress
IP Address form is invalid.
- Bitcoin Cash daemon deployment Bash script for CentOS 7.
- Bitcoin Cash daemon systemd service file.
- Bitcoin Cash logrotate configuration file.
- Bitcoin Cash configuration file.
For quick deployment please ensure:
- Root access to an updated CentOS 7 server.
yum install -y git
# Need to fill this in
Bind - Internet Systems Consortium:
https://www.isc.org/downloads/bind/
Bind with DLZ Support Documentation:
http://bind-dlz.sourceforge.net/
Many Bothans died getting this DNS server to you, honor them by sending me some Bitcoin(BTC), or Ethereum(ETH).
- BTC: 1K4N5msYZHse6Hbxz4oWUjwqPf8wu6ducV
- ETH: 0x76AB557F159a5048fA944566dbb18C834228d4e7
Released under the GNU General Public License v3. (Not sure this is even valid)