Brain,
Are we saying that ampr.org names and presumably 44 addresses are only valid if they have a gateway associated with them?
I've had addresses with dns entries allocated since the early 90's which I use from time to time for testing on rf networks which don't have an associated gateway. The chances are that by now the only record of that allocation is the DNS entries. I guess I could just abandon them and request a new allocation, and attach it to a dummy gateway.
73, John G8BPQ
-----Original Message----- From: 44Net [mailto:44net-bounces+john.wiseman=cantab.net@hamradio.ucsd.edu] On Behalf Of Brian Kantor Sent: 18 January 2016 21:18 To: AMPRNet working group Subject: Re: [44net] Nevada IP Assignments
(Please trim inclusions from previous messages) _______________________________________________ On Mon, Jan 18, 2016 at 12:57:56PM -0800, Harold (K7ILO) wrote:
I would like to know if these are in use so that the amprhost file can be update by me getting rid of them if possible.
Harold, If you didn't assign them they are probably no longer in use. Data in the AMPR DNS goes back some 30 years so much of it is obsolete.
In particular, there are only two subnets of 44.125.0.0/16 that are registered as having gateways to them: 44.125.2.0/24 44.125.10.0/24
Thus of all those you listed, only DNS entries in those two subnets are likely to be in use.
It's been suggested that AND'ing the DNS A record IP addresses with the valid subnets list would clean up a LOT of the obsolete DNS entries.
This is something that can be done mechanically by a series of scripts. If someone wants to do that and generate a list of entries to be deleted, we'd be quite a bit further along, I think. Does anyone see any flaws in this? - Brian
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net