Dear ProBIND Community,
After careful consideration, I've decided to archive this project due to time constraints and the challenges of maintaining it on my own. I want to express my gratitude to everyone who has contributed and supported ProBIND over the years.
Maintaining ProBIND has been a rewarding journey, but the demands of my current commitments prevent me from giving it the attention it deserves.
I believe in the potential of this community to carry the project forward. If you've benefited from ProBIND or have a passion for it, I invite you to consider contributing. While new issues and pull requests cannot be submitted directly to this repository, you can fork the project, make changes, and share your work.
Thank you for your support and contributions in the past.
Best regards, Paco Orozco
ProBIND3 is a web application designed for managing the DNS zones for one or more servers running the ISC BIND DNS server software. It works best for companies that need to manage a medium-sized pool of domains across a set of servers.
The application has been written using Laravel framework. It stores its data in a MySQL, Postgres database (see Laravel Database Backend) and generates configuration files for BIND on-demand.
ProBIND3 is meant to be a time-saving tool for busy administrators, aiding in managing the configuration of DNS zones across multiple servers. It is intended for use by those already familiar with the components of a DNS zone file and who understand DNS concepts and methods.
This software acts as a configuration repository to help keep zones well-maintained and has several helping tools to ensure that common DNS issues are minimized.
-
Although ProBIND3 uses a database to store zone data, it is not a replacement backend for ISC BIND. ProBIND3 merely creates the proper zone files for use with the default configuration method of BIND. If you are looking for a live SQL backend for ISC BIND, this is not one.
-
ProBIND3 is not a tool for those unfamiliar with DNS concepts. It assumes you know the differences between a CNAME and an A record. It also assumes you know about SOA records, what a lame server is, and what glue is.
-
ProBIND3 is not the ultimate solution to DNS management. It fits the needs of those who develop it, and it is hoped that others will also find it useful.
See our CHANGELOG file in order to know what changes are implemented in every version.
- PHP 8.1+ with
gmp
extension. - A supported relational database and corresponding PHP extension.
- Composer.
Laravel Sail is a light-weight command-line interface for interacting with Laravel's default Docker development environment. This will create several containers to implement the application needs. An Application server, a Database server and a Sample server (with SSH access).
Prior to this installation, you need to have installed this software:
-
Clone the repository locally
git clone https://github.com/pacoorozco/probind.git probind cd probind
-
Copy
.env.example
to.env
.NOTE: You don't need to touch anything from this file. It works with default settings.
-
Install PHP dependencies with:
NOTE: You don't need to install neither PHP nor Composer, we are going to use a Composer image instead.
docker run --rm \ --user "$(id -u):$(id -g)" \ --volume $(pwd):/var/www/html \ --workdir /var/www/html \ laravelsail/php81-composer:latest \ composer install --ignore-platform-reqs
-
Start all containers with the
sail
command../vendor/bin/sail up -d
-
Seed database in order to play with some data
sail artisan key:generate sail artisan migrate:fresh --seed
-
Point your browser to
http://localhost
. Enjoy!NOTE: Default credentials are
admin/secret
.
If you have issues with ProBIND3, you can report them with the GitHub issues module.
Please see CONTRIBUTING for details.
ProBIND3 is released as free software under GPLv3
ProBIND was originally developed by Flemming S. Johansen as part of his duties as resident DNS manager at Proventum Solutions. Later, a fork of ProBIND called ProBIND2 was developed by Alexei P. Roudnev, a senior network/software engineer, at Exigen Group LTD.
With both projects lying dormant for a number of years, Michael Johnson, Systems Administrator at PhD Computing, attempted to revive the ProBIND project. The enhancements made in ProBIND2 were merged in and development were once again resumed.
Later, in 2016, Paco Orozco recoded all this application using Laravel Framework to bring a new version of this software. It was named ProBIND3.
See AUTHORS for a complete list of contributors.