> Unless Hotmail is still silently deleting automated messages - it used
> to do that years ago, much to the annoyance of a place I previously
> worked for. Clients would complain that their booking confirmations
> would never arrive.
Hotmail is not usable for production. It is as unreliable as most Microsoft stuff.
Recently I sent a couple of messages about a network configuration problem to
a user on the Dutch hamnet, and later he claimed he never got them. But my own
outgoing mailserver has the logs of the delivery to the hotmail MX and accepted status.
Rob
> 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
> 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
> 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
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
> 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
> 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
> 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
