Re: [44net] Potential commercial use / TOS violation 44.144.50.0/24

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(a)mailman.ampr.org> On Behalf Of Rob PE1CHL via 44Net Sent: Saturday, November 20, 2021 10:54 To: Falcon Darkstar Momot via 44Net <44net(a)mailman.ampr.org> Cc: Rob PE1CHL <44net(a)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: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net