44net

44net@mailman.ampr.org

3194 discussions

Re: [44net] AMPR.Org DNS
by Rob Janssen 14 Jun '17

14 Jun '17

> I get no reply on an update mail to the ampraddr robot, but the changes did get processed... Ah, now I got the reply... too impatient, it got delayed by a greylister probably because the sender address changed. Rob

1 0

Re: [44net] AMPR.Org DNS
by Rob Janssen 14 Jun '17

14 Jun '17

> I don't plan to change the format of the new zone files; they are what is > being loaded into the nameserver. Please accept my apologies for the > difficulty. Ok no problem, I make the small changes required to ignore case and that TTL value when comparing the zone file to what comes out of my hosts->zone converter. Rob

1 0

Re: [44net] AMPR.Org DNS
by Rob Janssen 14 Jun '17

14 Jun '17

> I've switched the AMPR.Org and 44.in-addr master nameserver over to > using a new database and maintenance software. All seems to > be working correctly. > If you encounter any problems looking up a hostname or IP address > in the relevant ranges, please let me know. There is a change in the content of the downloadable zone file ampr.org.gz This causes problems in my scripts. I can modify the scripts, but first let's see if you can make them like before so similar issues for others could be avoided... Rob

2 1

missing encap.txt
by Michael Fox - N6MEF 14 Jun '17

14 Jun '17

The encap.txt file is missing from the portal. The last "encap.txt-<date>" is encap.txt-20170714073337 Starting after that, there are some "new_encap_<date>" files. But no "encap.txt". Michael N6MEF

3 2

Re: [44net] DNS Cleanup
by Rob Janssen 13 Jun '17

13 Jun '17

> Ok, they're gone too. What about > pe5hwg IN A 62.108.10.22 > which appears to be an anomoly, being outside net 44. Hmm that is a strange one! I don't think I added that, and pe5hwg is not a valid callsign. The IP address is in the Netherlands, though. Maybe you can still trace who submitted that? Rob

2 1

Re: [44net] DNS Cleanup
by Rob Janssen 13 Jun '17

13 Jun '17

> There were 23 44.137 addresses on the list of potential deletions. > They have been removed from the list. Thanks! There are 13 CNAME records as well: pd1aay IN CNAME pe1sac pe2ro IN CNAME pa7o links.pi1ehv IN CNAME pi1ehv pi8brd IN CNAME pi1brd www.pi8cdr IN CNAME pi8cdr smtp.pi8cdr IN CNAME lx.pi8cdr pop.pi8cdr IN CNAME lx.pi8cdr ns.pi8cdr IN CNAME lx.pi8cdr news.pi8cdr IN CNAME lx.pi8cdr ftp.pi8cdr IN CNAME pi8cdr pi8dec IN CNAME pi1dec pi8rmd IN CNAME pi1rmd sys2.pi8shb IN CNAME sys2.pi1shb Rob

2 1

Re: [44net] DNS Cleanup
by Rob Janssen 13 Jun '17

13 Jun '17

> Returning to the perennial subject of cleaning up the AMPR.Org DNS > database, Neil Johnson has done a thorough job of investigating the > entries in the current database. He has generated a file available from > the gw.ampr.org anonymous FTP server "Hosts-TBD.txt" which lists 2,045 > callsign-based entries in the DB where > 0. They're in the current AMPR.Org DNS. > 1. They're not found in active entries on QRZ.com. > 2. They're not found in the online Callbook database. > 3. They're not in the portal. > 4. They're not in HamNet.de. > 5. They were NOT entered into the AMPR.Org DNS after 2011. > 6. Or they are listed as expired in QRZ. All hosts in the 44.137.0.0/16 network are validated against the license authorities' callsign list on a weekly basis and expired licenses are deleted. Entries have been re-confirmed in 2014 and 2016 by sending a mailing and news bulletin and keeping only those entries for which a mail reply was received or that were otherwise confirmed as still active. About 1/3 of the hosts were deleted in 2016. Please don't delete further hosts from 44.137.0.0/16 (hostnames p[a-i][0-9][a-z]* ) Rob

2 1

Which FTP server to use for encap.txt?
by Michael Fox - N6MEF 13 Jun '17

13 Jun '17

I've been downloading the encaps.txt file from portal.ampr.org. Mostly, that's been OK except for the recent outage and some hick-ups in the data a year or so ago. Now the file is also on gw.ampr.org (if I understand correctly) in a slightly different format (<sigh>). The question is: which is the better source to use, considering likely uptime (network reliability, UPS, etc.) and reliability of data (fewest transforms from original data, etc.)? Thanks, Michael N6MEF

2 2

Re: [44net] DNS Cleanup
by William Lewis 13 Jun '17

13 Jun '17

Any way in which we will know what is getting deleted ? At 05:59 AM 6/13/2017, you wrote: >Returning to the perennial subject of cleaning up the AMPR.Org DNS >database, > >I propose to delete these entries from the AMPR.Org DNS around July 1st. > - Brian ---------- Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) ---------- William Lewis, 51-701 / KG6BAJ Deputy Chief Comm Reserve Officer (North) Deputy State RACES Officer (North) Communication Reserve Unit California Governor's Office of Emergency Services (530) 648-4920 Cell <mailto:wlewis@acscalifornia.org>wlewis<mailto:wlewis@acscalifornia.org>@acscalifornia.org **Confidentiality Notice: This e-mail, including any attachments, is for the sole use of the intended recipients and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient please notify the sender by reply e-mail and destroy all copies of the original message**

2 2

Re: [44net] 44Net Digest, Vol 6, Issue 112
by Gustavo Conrad 11 Jun '17

11 Jun '17

Hi Brian, thanks for your explanation. I was not aware of that requirement. I thought that every entry in the encap file, either host or network, it was fully routed. I will email Pedro LU7ABF to ask for the update. Also thanks to Brian N1URO and Tom SP2L for their feedback. 73! Gustavo LU7WA Date: Fri, 9 Jun 2017 20:44:38 -0300 > Date: Fri, 9 Jun 2017 17:56:14 -0700 > From: Brian Kantor <Brian(a)UCSD.Edu> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] Routing problem? > Message-ID: <20170610005614.GB9749(a)UCSD.Edu> > Content-Type: text/plain; charset=iso-8859-1 > > Amprgw filters at the per-host (/32) level. Each host which is to receive > traffic from the Internet into AMPRNet must individually be listed in > the permissions file, which is built from the AMPR.ORG DNS 'A' records. > > The only host on your subnet which is listed (and therefore is the only > one authorized) is 44.153.164.5. If you want .6 or other hosts on your > subnet to be able to communicate with the Internet, you will need to > have your local coordinator add them to the DNS for you. Or I can do it. > - Brian

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net