7 Feb
2016
7 Feb
'16
9:42 p.m.
On Sun, Feb 7, 2016 at 10:24 PM, Eric Fort <eric.fort(a)gmail.com> wrote:
Could this whole mess with DNS be handled and resolved
in a totally
different way? I.E. Delegation? How about a simple decree that says DNS
entries are to be handled similarly to netblock leases and for a similar
time period. Past that allow for zone delegation. It would work like
this... I go to my local coordinator with a request to join amprnet. My
coordinator discusses with me what size netblock I need and assigns
callsign.ampr.org.
This is very similar to how I set up a multi-master replicated
geo-redundant DNS for the company I work for (MSP). Our customers
don't know they have the ability to edit their own DNS right now, but
the functionality is there. I used open source projects such as
PowerDNS, Tungsten Replicator, MariaDB/Percona/MySQL, and a web
mangement front end for PowerDNS called PowerAdmin. Replacing the
existing TinyDNS (DJB DNS) was a pretty simple process, and during the
migration to the new DNS we cleaned up hundreds of old records.
The PowerAdmin project has an ACL system, which allows specific users
to modify their owned zones. Zones can have multiple owners.
Behind it all is a relational database, which would make any
organizationally required customization easy.
--
Rial F Sloan II
N0OTZ
Georgia Amateur Radio Data Network (GARDN) Administrator
AMPRNet Volunteer Coordinator - State of Georgia