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.
Rob
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.
On 17/06/20 06:51, Dave Gingrich via 44Net wrote:
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 have two allocations. One is dedicated to IRLP and Echolink services - the vast bulk of those IPs are being used for a bunch of Echolink proxies, with some IRLP and D-STAR infrastructure also making use of this block.
The other I use here, and plan on putting some of that to RF in some form (packet radio, higher speed data, etc). The parts not on air are supporting infrastructure that's running here.
I've got nothing against providing DNS information, beyond having a convenient means of doing so. As both of my allocations are /24s, running my own reverse DNS is feasible, and I have servers I can set the zones up on already, and am considering that option.
-
Dave Gingrich -
Rob Janssen -
Tony Langdon