I am not sure what you mean by feared, but no, my allocations are not supporting the
AMPRnet per se. If by AMPRnet you mean the legacy BBS style network of gateways and
tunnels. I am issuing OpenVPN certs to provide public IP addresses to IRLP voice
repeaters, where public IPs are troublesome to get, such as where cellular access to the
Internet with private IP is the only thing available. Parts of the IRLP infrastructure are
in 44-land, including
server4.irlp.net in Sydney or
server3.irlp.net in Chicago. It is
absolutely 100% Ham Radio. But I wouldn’t call it AMPRnet in the legacy or traditional
sense. I have had these allocations for over 5 years (Australia less than that).
I am definitely not interested in opening my nameservers up to anyone I do not know (so
mainly only my other nameservers). You can use dig -x like everyone else.
I signed the license agreement like everyone else that has a /24 or larger allocation, and
I stand by all the promises made there in.
--
Dave Gingrich, K9DC
Indianapolis, Indiana USA
On Jun 16, 2020, at 15:19, Rob Janssen via 44Net
<44net(a)mailman.ampr.org> wrote:
The reason I did this was because I needed
PTR records in something other than
ampr.org.
I already feared that it was to conceal non-AMPRnet usage...
This makes it all the more important to have zone transfer capability so the data can be
used to validate against local policies.