New subject: DNS cleanup

7 Feb 2016

...
  Prior to flaming me, perhaps you should get your facts
straight? 
...
  I have done several maintenance jobs and bug fixes on
the Portal over the past couple of years, as and when they are reported to me. I’m working
on a new feature right now that was requested. 
...
  If you have a problem you only need to contact me and
ask for assistance, but I am not good at reading minds I’m afraid. 
...
  As for the DNS code in the Portal, it has been ready
for over a year now, but Brian wanted me to hold off making it live until the current DNS
can be cleaned up - hence this push to do just that. 
...
  As to your other comments regarding how the portal
operates, that’s your opinion, which you are entitled to, but I originally wrote the code
based on requirements and input from other folk, I didn’t just “make it up” myself.

...
  Of course, if you want to offer your time re-write
some of the code, or add new functionality then please lets talk, I’ve been asking for
help on this for some time now, but apart from Tom who kindly provided (and still
provides) the Polish translation, no-one else has done anything. And before anyone goes on
about “open source” again, the code IS open source to the amateur radio community, just
not the general public as it doesn’t need to be, if you want access to the code repository
you only need to ask and it will be provided. 

Chris,

I have brought up the topic of (impossibility of) editing subnets a long time ago.
I have also reported the problem with registration of existing allocations (the user
cannot specify what they want to register, only request a new allocation), and requested a
way to delete open requests that cannot be completed.
And a few months ago I requested that, facing the impossibility to delete a subnet without
also deleting all its children and realizing that adding this may be nontrivial, you
manually delete the 44.137.24.0/22 subnet that was erroneously created long ago, without
deleting the subnets that are now under it.

Apparently in the requirements and input you received the migration of existing
allocations was not included.  I seem to remember that this has been discussed and
apparently it was downplayed as not important, but I don't agree with that.
In my opinion, it should be possible to migrate existing allocations to the portal system
when the holder desires to do that.
Without such functionality, we cannot request all the existing users to register
themselves and find out what to do next.

I am doing a lot for the local amateur digital network here, and I have to select what
other projects I join.  I cannot be active in all of them.
You have to understand that, contrary to some other areas, we are actively developing and
using the network, and we require a system that works for us.
So until now we have chosen to not register all the IP allocations via the portal, but
only the required minimum that is the IPIP tunneled space, waiting for suitable
functionality.
In the DL/OE HAMNET the situation is the same, and there they developed their own system,
HamnetDB.

I understand that it is a spare time effort and other activities have priority, but we
cannot live with a system part that keeps us back from progress forever.
When there are problems or changes, there has to be some outlook that they will be fixed
some day.  Does not need to be tomorrow.
Maybe you should join efforts with the HamnetDB people to merge the part that now handles
the IPIP tunnel system with their system, which in other areas is much much more flexible
and more like what we require.
(although of course there always are wishlist items, e.g. because of things that are
incompatible with our local license system)

Rob

Re: [44net] DNS cleanup