21 Nov
2021
21 Nov
'21
5 p.m.
Why not? When I assign subnets to users, I put a DNS name subnet.callsign.ampr.org at
the
network address of the subnet. Works fine.
Why do we always have to make things so complicated and suggest that issues we have can
only be solved by deploying a facility we do not have? Everything comes to a dead stop
every time.
It is easy for coordinators to submit a bulk update for DNS for the addresses they
manage.
No idea why not all of them do it.
Also, I think that such owner info should not be updated by the user of subnet, but by the
coordinator.
Having it done by the user means there is no more oversight on what they enter there, and
they
can easily set some space they want to use commercially to some nonexisting- or someone
elses
callsign, which we then will have to check and cleanup later. Not a good idea IMHO.
Rob
On 11/21/21 1:28 AM, Matt - VK2FLY via 44Net wrote:
Reverse DNS is not a mechanism to identify end users
of subnet's. That mechanism already exits it's called whois. In a perfect would
the 44net registry would allow users to update their own whois entry from the portal.
Matt