20 Nov
2021
20 Nov
'21
4:53 a.m.
It probably almost never is a problem. There are so many AMPRnet addresses in use
without
a proper registration in ampr.org DNS (which automatically creates the reverse DNS record)
that
this cannot be the explanation for all of them.
Apparently the DNS for 44.144 is very incomplete, the maintainer should bulk-update it.
The DNS entries for 44.137 are completely in sync with the hosts file and addresses not
appearing
in that list are filtered at the gateway, just like on the UCSD gateway. Everyone should
do that.
Rob
On 11/20/21 10:28 AM, Falcon Darkstar Momot via 44Net wrote:
That could raise unexpected technical problems when
rDNS is expected to be a particular thing. If someone wants to do that, they'd do
better to create a TXT record like 1.23.31.44.in-addr.arpa IN TXT "AF7MH". But
we know who the assignee is already!
AF7MH
On 2021-11-20 00:38, Rob PE1CHL via 44Net wrote:
> Note that none of these addresses (nor the other ones posted) have reverse DNS.
> I think we should make DNS entries (with callsign) mandatory for all allocated
AMPRnet addresses!
>
> Rob