On 2023-03-09 10:33, Grant Taylor via mailop wrote:
On 3/9/23 9:45 AM, Michael Peddemors via mailop wrote:
<clip>
AS well, you 'could' change default PTR's for segments used differently.
I find the idea of requiring PTRs to contain a magic string to be
unappetizing at best and appalling at worst.
IMHO *NOBODY*, and I mean absolutely /nobody/ gets to tell me what I
name my own system. That extends to things that tie into the host name,
e.g. rDNS PTR records.
This would also be predicated on there being a single string that the
entire industry would accept. I find this to be extremely unlikely.
Okay, better expand on what I am saying.. say you have a bunch of IPs
from Linode, .. you 'might' want to indicate better what they are for..
eg..
sharedhosting.hisdomain.com
mailout.hisdomain.com
etc..
If the PTR's still reflect the generic
li1072-208.members.linode.com
He probably won't get them removed from an RBL..
At least you are asking how you can do things differently.
I mentioned to Michael -- in a direct email -- that I wonder if there is
an opportunity to put something in parent DNS zones in the .arpa
sub-domains, much like DS records for DNSSEC go in parent zones, so that
an IP provider (or at least naming authority) can specify that a range
is delegated to another entity.
Usually this is ONLY done for a /24 or greater by upstream providers..
(While it can get done for smaller blocks, you end up with that ugly
double PTR record, one from the provider and one from your DNS server)
I also mentioned that miscreants would be likely to abuse this and
artificially divide their IP space so that bans on some parts would not
effect other parts. Hence the need to have a larger addressing / naming
authority provide this.
Yes, we see that.. it does occur.. but pretty obvious usually. Take a
look at the OVH guys with fake ownership.. but it can be used to help
positively identify good operators, and that value is important as well.
I think the distributed nature of rDNS could work well for this /if/
there was an agreed upon way to signal this /and/ we could get
addressing / naming authorities to support it.
I know there has been a lot of Linode 'slagging' on the list, but it
isn't as bad as some other networks.
I'm using Linode and still having reasonable luck. Though I do see
evidence that the neighborhood is running down in some places.
Strange, wish Linode would pipe up on this on list..
Some segments are REALLY bad, and other segments never generate a
complaint.. They must be differentiating internally some of their
customer signups..
As a customer, ask Linode to provide 'rwhois' for you.
I have done exactly that multiple times. Each and every time they say
that they don't support it.
If the hosting provider doesn't provide 'rwhois', speak with your feet.
Even GoDaddy offers it, and as much talk about bad GoDaddy, a person
with a correct 'rwhois' can usually get off an RBL a LOT quicker.
--
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada
This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
