Subject:
Re: [44net] DNS (was: Nevada IP Assignments)
From:
Neil Johnson <neil.johnson(a)erudicon.com>
Date:
01/19/2016 02:10 AM
To:
AMPRNet working group <44net(a)hamradio.ucsd.edu>
The initial script is done:
" 44.225.65.22 ","GATENOTFOUND"
" 44.50.192.22 "," 108.160.233.78"
" 44.225.66.220 ","GATENOTFOUND"
" 44.225.65.220 ","GATENOTFOUND"
" 44.225.64.220 ","GATENOTFOUND"
" 44.225.66.221 ","GATENOTFOUND"
" 44.225.64.221 ","GATENOTFOUND"
" 44.225.66.222 ","GATENOTFOUND"
" 44.225.64.222 ","GATENOTFOUND"
" 44.225.66.23 ","GATENOTFOUND"
" 44.225.65.23 ","GATENOTFOUND"
" 44.50.192.23 "," 108.160.233.78"
" 44.225.66.24 ","GATENOTFOUND"
and so on
Of the 36059 address records 30176 don't have a gateway associated with
them. Seems kind of a large amount. I'll do some more sanity checking.
This is going to fail big time!!
That 44.225 network is probably the most active net-44 network in the world, but it is
not gatewayed to internet. People will not like it when you try to delete that!!
Also, again the proposal is made to transfer things to the portal. I do not consider the
portal ready for production use for this, and I question if it ever will be. Changes to
functionality and replies to questions are so far between that I don't think the
maintainer
has enough resources to keep this project moving. Note I don't want to blame him
for
this in any way, but I don't think we should become more dependent on it than we are.
Rob