44net

44net@mailman.ampr.org

3196 discussions

Re: [44net] Verifying the identities of IP coordinators
by Rob Janssen 20 Jan '16

20 Jan '16

> Re: [44net] Verifying the identities of IP coordinators > From: > Don Fanning <don(a)00100100.net> > Date: > 01/13/2016 05:56 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > On Wed, Jan 13, 2016 at 6:25 AM, Brian Kantor<Brian(a)ucsd.edu> wrote: > > I just thought of another possibility. We could ask that the regional > coordinators do an audit of their IP spaces in conjunction with the > above suggestions as they're likely to have closer relationships with > the end user or be more familiar with the record keeping of their > countries amateur radio licensing. Then we can check off that IP > space as "claimed" or "reclaim" it back into the pool. > I have made an effort to do that. I tried to contact all hams that are in the current allocation for the Netherlands, and asked them if they want to maintain their allocation. As a result, some have replied they no longer want to use it, and I have deleted those allocations. The ones that confirmed their allocation I put on a list with a datestamp. But the vast majority of the hams could not be reached. I have no uptodate contact info and even the old contact info is difficult to access (it is a folder in my mail program that stores all original requests starting in 2002, I don't even have those for the addresses requested before 2002). I also regularly delete the allocations for hams that no longer appear in the official callsign listing for the Netherlands. (I have done this every year, but recently I have done it weekly because starting from this year there is a fee for keeping an amateur callsign and lots of inactive hams have removed their registration as a result) I only keep the registrations in a hostsfile and use a script to send the updates to the mail robot. As an afterthought, I should have kept a file with more info like date of registration and contact address for each entry, but it would require a filtering system so this information does not end up in the publicly visible file. I like to keep everything in a textfile as opposed to some database with a web form frontend, because it allows me to browse through the file to see where a new allocation is to be put, something lacking from many address allocation systems including the amprnet portal. Rob

6 5

Re: [44net] DNS Clearout
by Rob Janssen 19 Jan '16

19 Jan '16

> Subject: > Re: [44net] DNS Clearout > From: > "John Wiseman" <john.wiseman(a)cantab.net> > Date: > 01/19/2016 04:17 PM > > To: > "'AMPRNet working group'" <44net(a)hamradio.ucsd.edu> > > > Thanks, Brian, > > I've just checked on the portal, and it seems I'm too late - they have > already been allocated to someone else. (44.131.4.18-21). So they won't get > removed by the clearout, but I'll need to replace them anyway. But it > highlights a problem with your suggested approach - It won't pick up unused > names which are in address ranges that have been reallocated. And glancing > though the uk dns records I suspect that applies to a lot of entries. > > But I can't think of a better solution, and I guess an incomplete clearout > is better than none! > > 73, > John Note that your entries are registered in the ampr.org DNS, but the portal apparently does not respect that. This is one of the problems with the way the DNS part of the portal works: there is no way to see what is already in use before allocating something new. But nothing has been done about that yet, and the issue is open for many years. Rob

1 0

Re: [44net] DNS (was: Nevada IP Assignments)
by Rob Janssen 19 Jan '16

19 Jan '16

> 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

2 1

AMPRNet DNS cleanup
by Don Fanning 19 Jan '16

19 Jan '16

Last year I tried to attack the task of cleaning up the DNS. Brian at one point did an AND against the gateway subnets with the DNS and it produced ~19k A records - hundreds of times what is valid or even being used. So as a curiosity exercise, I wrote some script to import the DNS into MySQL. The result was 16653 unique callsigns in the DNS and 2211 aliased/bad call signs as of June 2015. I then imported the FCC amateur database and compared it to US (A,K,N,W) callsigns - that produced 3742 unique US callsigns matching the DNS. Out of those, 1373 callsigns matched an expired, canceled or terminated license. This doesn't take into account all the vanity call signs for the 1x2/2x2/2x1/1x3 callsigns which may be attributed to another operator. While we can get good grips on the US callsigns, as soon as it crosses an international border, it goes to pot as every country has their own licensing structure. Many do not have online databases. So that's what we're faced with. Ideas welcome as to how we can validate the DNS tables.

2 2

Re: [44net] (no subject)
by Steve L 19 Jan '16

19 Jan '16

Neil, A couple years ago I created a script to do this. http://www.qsl.net/kb9mwr/wapr/tcpip/checkampr.txt Anyone is welcome to use it/modify whatever.

1 0

Updating Records
by Peter Mallett 19 Jan '16

19 Jan '16

Hi All, I have been looking at my allocations and would like to weed out the dead wood. What is the easiest way to do this ? Regards ..... Peter ZL2BAU

2 2

Re: [44net] Proposal for Cleaning up ampr.org DNS file
by William Lewis 18 Jan '16

18 Jan '16

That wont work, as the DNS function of the portal is not live yet. At 12:13 PM 1/18/2016, you wrote: >I could then attempt to send an e-mail message asking the call sign owner >to update their DNS entries via the portal. ---------- Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) (530) 263-1595 (Home/Office) ______________________________________________ ---------- This message is for the designated recipient only and MAY CONTAIN PRIVILEGED OR CONFIDENTIAL INFORMATION. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this E-mail is prohibited.

1 0

Proposal for Cleaning up ampr.org DNS file
by Neil Johnson 18 Jan '16

18 Jan '16

All, I've hacked together a script that goes through the ampr.org DNS zone file and pulls out callsigns and related A, CNAME, and MX records. Example: CALL: N0SFH dhcp-20.n0sfh IN A 44.50.192.20 dhcp-21.n0sfh IN A 44.50.192.21 dhcp-22.n0sfh IN A 44.50.192.22 dhcp-23.n0sfh IN A 44.50.192.23 dhcp-24.n0sfh IN A 44.50.192.24 dhcp-25.n0sfh IN A 44.50.192.25 dhcp-26.n0sfh IN A 44.50.192.26 dhcp-27.n0sfh IN A 44.50.192.27 dhcp-28.n0sfh IN A 44.50.192.28 dhcp-29.n0sfh IN A 44.50.192.29 dhcp-30.n0sfh IN A 44.50.192.30 gw.n0sfh IN A 44.50.192.1 n0sfh-1 IN A 44.50.192.5 Line count= 13 I could take the call signs and run them against QRZ.com (I have a XML subscription) and/or the Radio Amateur Call Book Data (The "Flying Horse" CD - I'm willing to buy the data). I could use that data to 1) determine if the call sign was still active 2) try to find an e-mail address associated with the call sign. I could then attempt to send an e-mail message asking the call sign owner to update their DNS entries via the portal. In the e-mail we could give the call sign owner 60-90 days to update their DNS entries or they would be deleted. I came up with 17899 potential call signs in the zone file. I would need: 1. Permission from the ARDC to send e-mails on its behalf. 2. A way to whittle down the file further, if possible. 3. Volunteers to translate the notification e-mail into multiple languages. 4. Someone who has an ISP or mail host willing to allow the sending of 10's of thousands of e-mails without it getting flagged as SPAM (I would want to try and contact each call sign owner with a valid e-mail at least three times before the deadline). 5. Access to the portal's DNS database to determine if someone registered their entries. Thoughts? -Neil -- Neil Johnson

2 1

Why Subject lines have squat to do with message content.
by Jerry Kutche 18 Jan '16

18 Jan '16

Guys I am not a moderator, owner or anything else... just a quickly becoming disinterested Coordinator in this group. 1 Reason the thread topics are out of whack. Take this one.. below titled (Verifying the Identities of IP Coordinators,)yet contains only discussions about DNS. It is no longer about identities, of IP Coordinator yet it goes on and on and on about DNS under a misleading Subject line. Then there is the THREAD more correctly titled Dynamic Addresses. How is anyone following both of these and making sense out of them. ? I really do not care what we talk about.. But I personally like being able to pick and choose what I read about.. without having to fish every message. When we are talking about orangutans, under a title of Planets from Space.. Sure is miss leading.. Just todays gripe.. Carry on I am sure nothing will change. Also remember to... > (Please trim inclusions from previous messages) 73 Jerry N9LYA

1 0

Re: [44net] Verifying the identities of IP coordinators
by Assi Friedman 18 Jan '16

18 Jan '16

My guess would be that it's not a DNS server load issue but more of an administrative / architecture issue. If stale/abandoned entries are not purged, it makes the task of design and coordination a tad more difficult since new hosts/networks have to work around the already assigned ones. Assi kk7kx -----Original Message----- From: 44Net [mailto:44net-bounces+assi=kiloxray.com@hamradio.ucsd.edu] On Behalf Of R P Sent: Sunday, January 17, 2016 10:18 PM To: AMPRNet working group <44net(a)hamradio.ucsd.edu> Subject: Re: [44net] Verifying the identities of IP coordinators (Please trim inclusions from previous messages) _______________________________________________ I ask again What is so important to clean the DNS from all the amount of unused hosts ? is it a matter of load on the DNS that result in a slow response ? or any other effect im not aware of ? The only thing i can think of is making zone transfer of big file twice a day but in this days transferring even 10 MegaByte file each day consider nothing Maybe Brian can answer this ? However to answer your question Authorized users can change the DNS data there is a format needed to be sent in the email that the robot know to inter-prate something such as : <host name > <add or delete> <what kind of record should it be (MX A etc)> <Ip adress> you send each host as a single line and you can more then one line Since the robot have a format checking mechanism you dont have to be a DNS expert in order to add or delete hosts specially if you want only to add host name and not complex things such as MX records or CNAME Regards Ronen - 4z4zq http://www.ronen.org ---------------------------------------------------------------------------- ------------------------------------------ 1. What information must a coordinator send to the ampr.org DNS to create/modify a listing? 2. Is there a standard entry format for the information a coordinator sends in, or is it parsed by hand? 4. Is it possible for me to reformat the existing files, knowing little about DNS? hth. 73, Bill KW4OC _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net