16 Jun
2020
16 Jun
'20
2:22 p.m.
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
16 Jun
16 Jun
3:51 p.m.
New subject: Reverse DNS and access to DNS info
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
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.
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. 
11:32 p.m.
New subject: Reverse DNS and access to DNS info
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.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
1622
days inactive
1623
days old
2 comments
3 participants
participants (3)
-
Dave Gingrich -
Rob Janssen -
Tony Langdon