To a limited extent, they can --
The Description is taken from the IP allocation as input by the requestor The Locator is taken from the User Profile
whois -h whois.ampr.org 44.24.130.0
Complete editing could lead to the creation of bogus responses on whois.
Perhaps we could add the associated email with the OrgAbuseEmail and OrgTechEmail?
On Sat, Nov 20, 2021 at 4:32 PM Matt - VK2FLY via 44Net < 44net@mailman.ampr.org> 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
On 21/11/21 2:05 am, Ruben ON3RVH via 44Net wrote:
It is true that the 44.144 reverse zone is almost empty, however it -
currently - is only updated at end user's request.
There - currently - is no filtering on valid PTR records for internet
access at our border, however we are designing a new connectivity system for our users and can incorporate that.
Whether or not everyone should do that is up for debate imo and if the
majority should decide that and UCSD follows and makes it a rule of thumb then indeed everyone should do that. Maybe discussion to be held with the TAC?
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf
Of Rob PE1CHL via 44Net
Sent: Saturday, November 20, 2021 10:54 To: Falcon Darkstar Momot via 44Net 44net@mailman.ampr.org Cc: Rob PE1CHL 44net@pe1chl.nl Subject: Re: [44net] Potential commercial use / TOS violation
44.144.50.0/24
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
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-- _____ _____ |___ |___ / Matt Perkins VK2FLY (advanced) / / |_ \ Woolloomooloo NSW (QF56od) +61403571333 matt@vk2fly.com / / ___) | A pround member of ARNSW, The WIA, /_/ |____/ And the Waverley Amateur Radio Society.
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net