Re: [44net] Dumb question - 44.130 IP address? - 44net

7 Feb 2016

Hi group,
hello Thomas,
IIRC the initial assignment was in fact given to me by you and Paul, so 
I'm happy to hear from you again. :)

On 02/07/16 23:55, Thomas Osterried wrote:
...
  Hello,

 well, a longer tradition than the quite new portal are the country-wide IP-Koordinators.

 In DL, we have the coordination team of three people (dd9qp, dg8ngn, dl9sau) and we
delegate the responsibility of the local assignments to the regional coordinators. This
concept goes back to the last century.
  From the regional coordinator, Wolfgang had got the initial assignment of his IP
addresses. 
That is correct. And that was kind of "status quo" when I had to quit 
Packet Radio activity. But the first thing I found when I searched for 
infos on the current state of IP in PR was that my IP's no longer do 
exist (which in fact is not really the problem for me, as I really was 
not active for a long time. So, no complaints on that from me, that's 
perfectly OK if there's some need for IPs.

...
  Some time ago, we did a clean-up of the old 44.130
packet-radio block in communication with the regional coordinators.

 What's with the portal? - I think we need discuss that. It had been no relevance for
us (since no one requested it), and I'm not sure, how it fits in a concept of the
country coordinator system (unless a country coordinator defines a
do-what-you-want-netblock for self-allocation - but how this may be integrated in a
working routing concept??). 
I think the portal would not work that good with a concept like the 
formerly used one with using the IP for granular routing over PR 
network. But I seem to remember discussions that the "routing feature" 
would not be needed any more and the whole german IP PR network should 
be seen as one big block (which I do not really support from my 
standpoint as sysadmin).

...
  Region ofr.de (44.130.62.0/24) was resigned
2013-07-31. Regional Coordinator was DL1NAT.
 The zone file of that region expired with serial 2004041601. Nine years after the last
update. forward- and reverse- entries were inconsistent: the reverse file had the serial
number 2002062201 (I assume 2 years before).

 I do not like to blame anyone, but it may be useful in that discussion. 9 (or 11) years
after the last coordination of the subnet and 2.5 years after your regional coordinator
stated that all records could be removed, you recognize that dg7nef, dg7nef-2 and
dg7nef-gate ( 44.130.62.20, .18, .19) have been passed back. 
And that lead to my problem with portal.ampr.org as I still had my own 
local acting DNS serving as "Master" for the zone on requests from my 
network, so I could at least keep the IP adresses I did contact in a 
state that did work for me. Yes, split DNS and multiple masters are an 
ugly thing. But it did work locally then.

...
  This emphasizes both, the difficulties we'll get,
even years after a clean-up, and on the other site the need to have a clean-up (the /24
had 57 entries (22%) and we finally got one complain (Wolfgang had 3 addresses -> 5 %).
For most cleaned subnets we got 0 responses at all). 
Well, in fact no complains from me so far, just a bit confusion on my 
side. ;)

...
  And imho, it also shows the country- / regional-wide
coordination concept makes sense. Currently, we've 35866 IN A records in ampr.org.
Imagine we'll have 10 requests a day on the list of the pool of every user, we all
will have to read the next 10 years about every individual issue. 