Subject: Re: [44net] Reboot (DNS) From: Brian Kantor Brian@UCSD.Edu Date: 09/13/2013 01:59 PM
To: AMPRNet working group 44net@hamradio.ucsd.edu
The goal is to have every DNS entry belong to someone who is registered with the portal, so that when that person becomes inactive (defined as no longer keeping their portal registration current despite annual reminders), the DNS entry will also become inactive, and after a year or so, be expunged. That way we can reclaim addresses and also prevent the DNS from being full of obsolete data.
What we have to work with is a database that has only the DNS information for the vast majority of its entries. For the past few years, it has also been recording the timestamp and author of the entry. So the plan in general (details are still to be worked out) is to convert entries which match registered portal users either in the hostname or in the author field. That will have the effect of leaving out most of the obsolete entries but should retain most relevant (active) ones.
What we have (again) learned from the first step, the migration of the gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again.
When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed.
But of course *some* validation has to be done.
Rob
So what do you propose ?
-Neil
On Fri, Sep 13, 2013 at 3:09 PM, Rob Janssen pe1chl@amsat.org wrote:
What we have (again) learned from the first step, the migration of the
gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again.
When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed.
But of course *some* validation has to be done.
Rob ______________________________**___________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/**mailman/listinfo/44nethttp://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.**html http://www.ampr.org/donate.html
The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
Thanks, Chris
What we have (again) learned from the first step, the migration of the gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again.
When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed.
But of course *some* validation has to be done.
Rob
Chris, I am replying to the group although my question will not be of interest to many others, apologies to most of you!
I have been silently following the discussions but too shy to ask, until now, what is happening in the UK? I have been out of the hobby for some years but may get back in (retirement pending) ... we had a few active stations in the Cambridgeshire area but when interest dropped the regional rep closed his gateway down of course. I would assume that management of the DNS for our entries would have delegated back upwards but I am not sure who to. I think the addresses we used were in the 44.131.29.0/24 range, from memory. It would be nice to think that we could just switch on again one day and carry on using those addresses but if there's a shortage of addresses in that range then I suppose that we should release them; however I suspect that isn't the case locally!
Do you know what the delegation chain (if I can call it that) is, down to our range/subnet?
As an observation, the allocation system we had seemed to be a little like a manual, heirarchical version of DHCP, with addresses allocated as needed by local agents who updated the DNS for you and in turn made requests for required subnet address ranges to agents higher up the chain. This thought makes me wonder if something like DHCP/DDNS might have a role in managing DNS in Amprnet?
Sorry to clutter the list, 73
Hello Steve
M1DUO in Cambridge is currently getting reset up on IP
Interest in Kent, Essex and West London currently coming back on line 73 de Paul g4apl SysOP GB7CIP
In message 4b60e51c-8d6c-4b77-b1d1-c74e6e977b62@email.android.com, Steve Platt steve.platt@ntlworld.com writes
(Please trim inclusions from previous messages) _______________________________________________ Chris, I am replying to the group although my question will not be of interest to many others, apologies to most of you!
I have been silently following the discussions but too shy to ask, until now, what is happening in the UK? I have been out of the hobby for some years but may get back in (retirement pending) ... we had a few active stations in the Cambridgeshire area but when interest dropped the regional rep closed his gateway down of course. I would assume that management of the DNS for our entries would have delegated back upwards but I am not sure who to. I think the addresses we used were in the 44.131.29.0/24 range, from memory. It would be nice to think that we could just switch on again one day and carry on using those addresses but if there's a shortage of addresses in that range then I suppose that we should release them; however I suspect that isn't the case locally!
Do you know what the delegation chain (if I can call it that) is, down to our range/subnet?
As an observation, the allocation system we had seemed to be a little like a manual, heirarchical version of DHCP, with addresses allocated as needed by local agents who updated the DNS for you and in turn made requests for required subnet address ranges to agents higher up the chain. This thought makes me wonder if something like DHCP/DDNS might have a role in managing DNS in Amprnet?
Sorry to clutter the list, 73
Please check your backlog of emails as I have one in limbo.
Willie, WJ3G
On 9/15/2013 3:56 AM, Chris wrote:
(Please trim inclusions from previous messages) _______________________________________________ The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
Thanks, Chris
What we have (again) learned from the first step, the migration of the gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again.
When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed.
But of course *some* validation has to be done.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
Hi Willie,
I have no backlog of emails pertaining to the gateway migration, I have processed all the ones I am aware of, so if you could resend to chris@g1fef.co.uk please, I will process it asap for you.
Thanks, Chris
On 15 Sep 2013, at 13:33, Willie Hein WJ3G wj3g@comcast.net wrote:
(Please trim inclusions from previous messages) _______________________________________________ Please check your backlog of emails as I have one in limbo.
Willie, WJ3G
On 9/15/2013 3:56 AM, Chris wrote:
(Please trim inclusions from previous messages) _______________________________________________ The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
Thanks, Chris
What we have (again) learned from the first step, the migration of the gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again.
When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed.
But of course *some* validation has to be done.
Rob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
On Sun, 2013-09-15 at 08:56 +0100, Chris spake:
(Please trim inclusions from previous messages) _______________________________________________ The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
I've had a few dating back to late spring. If you need me to resend please let me know offlist and I'll do so.
Yes please Brian, send any outstanding to chris@g1fef.co.uk and my apologies if I have overlooked any.
Chris
On 15 Sep 2013, at 13:46, Brian Rogers n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Sun, 2013-09-15 at 08:56 +0100, Chris spake:
(Please trim inclusions from previous messages) _______________________________________________ The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
I've had a few dating back to late spring. If you need me to resend please let me know offlist and I'll do so. -- 73 de Brian Rogers - N1URO email: n1uro@n1uro.ampr.org Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I'm stuck with that task due to several bugs in the portal. I have contacted Brian and Chris but there is no fix yet.
I was forced to stop using the portal due to those bugs. We are currently unable to proceed with the migration process due to issues with the portal.
I absolutely understand the necessity for up2date registrations, but unless all the portal features, necessary to avoid an expiration of an allocation, are in place and working flawlessly (or being fixed within a few days/weeks), discussions about expiration and reclaiming of resources are pointless.
73 de Marc, LX1DUC
On 15/09/2013 09:56, Chris wrote:
(Please trim inclusions from previous messages) _______________________________________________ The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
Thanks, Chris
What we have (again) learned from the first step, the migration of the gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again.
When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed.
But of course *some* validation has to be done.
Rob
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
-
Brian Rogers -
Chris -
G1FEF
-
Marc, LX1DUC -
Neil Johnson -
Paul Lewis -
Rob Janssen -
Steve Platt -
Willie Hein WJ3G