People -- we need the cleanup. I say, be aggressive. If an active DNS record gets deleted, just recreate it -- Sheesh.
Maybe you have not understood it, but we are actually *using* the network. For places where it is just a leftover of the packet radio days, I agree.
Today I deleted a number of old BBS records, and a few hours later I got a mail back that one that was still in use. We cannot do that for all 3000 active records.
Rob
Rob,
If you look in the file that Brian posted you will see that there are no 44.137.X.X (or 44.130.X.X) records in the list to be deleted.
So your DNS records should be okay.
Again the file is at: ftp://hamradio.ucsd.edu/pub/to-be-deleted.txt
-Neil
On Sun, Feb 7, 2016 at 2:31 PM, Rob Janssen pe1chl@amsat.org wrote:
(Please trim inclusions from previous messages) _______________________________________________
People -- we need the cleanup. I say, be aggressive. If an active DNS record gets deleted, just recreate it -- Sheesh.
Maybe you have not understood it, but we are actually *using* the network. For places where it is just a leftover of the packet radio days, I agree.
Today I deleted a number of old BBS records, and a few hours later I got a mail back that one that was still in use. We cannot do that for all 3000 active records.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
You have the user recreate it through the portal. Then they will have a portal account. On Feb 7, 2016 12:33 PM, "Rob Janssen" pe1chl@amsat.org wrote:
(Please trim inclusions from previous messages) _______________________________________________
People -- we need the cleanup. I say, be aggressive. If an active DNS record gets deleted, just recreate it -- Sheesh.
Maybe you have not understood it, but we are actually *using* the network. For places where it is just a leftover of the packet radio days, I agree.
Today I deleted a number of old BBS records, and a few hours later I got a mail back that one that was still in use. We cannot do that for all 3000 active records.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
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. I can then choose to manage my own zone or have someone manage it for me. In either instance the coordinator simply enters a pointer to the global DNS server for that zone. Those providing DNS services for ampr.org subdomains are permitted to do so for a predetermined period, say 1yr at which point DNS registration drops from DNS unless renewed. Note, IANA via their registrars seem to manage this quite well. Really the only difference is that we offer free name registration and fail to force the experation of unused names after a predetermined time period. Honestly we probably ought require a couple usd when someone registers a name.ampr.org with their coordinator. It would not be overburdensome and it would serve to fund the ongoing operational costs of ampr.org most of which atpresent seem to be borne by BMW and maybe berry few others. Is be in favor of basicly scrapping our current dns and simply reregistering everything. Let's take a clean start, then deligate zones to be handled by groups that know their users. Then only lease ampr.org subdomains for a finite time and require anual renewals.
Eric On Feb 7, 2016 5:11 PM, "John D. Hays" john@hays.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ You have the user recreate it through the portal. Then they will have a portal account. On Feb 7, 2016 12:33 PM, "Rob Janssen" pe1chl@amsat.org wrote:
(Please trim inclusions from previous messages) _______________________________________________
People -- we need the cleanup. I say, be aggressive. If an active DNS record gets deleted, just recreate it -- Sheesh.
Maybe you have not understood it, but we are actually *using* the
network.
For places where it is just a leftover of the packet radio days, I agree.
Today I deleted a number of old BBS records, and a few hours later I got
a
mail back that one that was still in use. We cannot do that for all
3000
active records.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
On Sun, Feb 7, 2016 at 10:24 PM, Eric Fort eric.fort@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.
-
Eric Fort -
John D. Hays -
Neil Johnson -
Rial Sloan -
Rob Janssen