On 4/14/2015 08:51, Colin Johnston wrote:
Get real, why make is hard for others to debug abuse issues, another
reason why blocks in place as no technical cooperation.
Because "others" has a subset = "dreaded anti-spammers".
--
The unique Characteristics of System Administrators:
The fact tha
On 4/14/2015 08:26, Colin Johnston wrote:
Because looks strange especially if the traffic is 100% bad Best
practice says avoid such info in records as does not aid debug since
mix of dec and hex
Which is precisely why spammers have been doing it for years.
--
The unique Characteristics of Sys
On 14/04/15 06:26, Colin Johnston wrote:
> Best practice says avoid such info in records as does not aid debug since mix
> of dec and hex
Can you please cite the best practice document where this is stated?
Thanks.
On Tue, Apr 14, 2015 at 10:09 AM, Pavel Odintsov
wrote:
> We use hexademical numbers in PTR for VPS/Servers because PTR's like
> "host-87.118.199.240.domain.ru" so often banned by weird antispam
> systems by mask \d+\.\d+\.\d+\d+ as home ISP subnets which produce
> bunch of spam.
Hi Pavel,
Actu
perfectly legal… the octal records confuse me more than the hex.
/bill
PO Box 12317
Marina del Rey, CA 90295
310.322.8102
On 14April2015Tuesday, at 5:36, Colin Johnston wrote:
> never saw hex in host dns records before.
> host-242.strgz.87.118.199.240.0xfff0.macomnet.net
>
> range is bl
On Tue, 14 Apr 2015 14:26:48 +0100, Colin Johnston said:
> Best practice says avoid such info in records as does not aid debug since mix
> of dec and hex
Odd. All the hex and decimal have proper indicators (initial 1-9 or 0x), and
should be easily understood by anybody who actually knows their nu
Yep, last time I've checked and internet isn't running on communism.
On 14/04/15 18:05, Rod Beck wrote:
> Private benefit is less than social (sum of private benefits across all
> affected parties) benefit.
User complain that his network slow and reliable. Check if its saturated
his link and tell him buy additional 10mbps/s, here is your profit.
If you really want fight bots, you need to track down and fight C&C in
first place. Otherwise you are fighting windmills.
http://arstechnica.com/tech-policy
Sounds like a textbook economics case of a network externality. The benefit to
the provider is far less than the benefit to the entire affected community.
Private benefit is less than social (sum of private benefits across all
affected parties) benefit.
Roderick Beck
Sales Director/Europe and t
There becomes a point though that doing nothing allows larger problems which
could have been nipped in the bud if sorted when issue was a smaller magnitude.
Profit when there is known bad traffic as a percentage and you known ignore it
is bad profit and does not help the greater good.
most folks
Transit traffic isn't issue, as upload/download ratio usually 1:2 or more.
As I said before when you already on edge of your profits, you don't
bother fixing these clients. Its not about best practice which I agree,
but business you are running, which is suppose to be profitable. And
fixing these
t;>>
>>> On 14/04/15 16:45, Chuck Church wrote:
>>>> Comic Book Guy would probably declare:
>>>>
>>>> "Worst Naming Convention Ever"
>>>>
>>>> Chuck
>>>>
>>>> -Original Message-
>>>&g
190
>>>>
>>>>
>>>> On 14/04/15 16:45, Chuck Church wrote:
>>>>> Comic Book Guy would probably declare:
>>>>>
>>>>> "Worst Naming Convention Ever"
>>>>>
>>>>> Chuck
>>>>
; dig -x 217.199.208.190
>>>
>>>
>>> On 14/04/15 16:45, Chuck Church wrote:
>>>> Comic Book Guy would probably declare:
>>>>
>>>> "Worst Naming Convention Ever"
>>>>
>>>> Chuck
>>>>
>
Colin, I understand that you would like everyone on the Internet to
behave in a way that you consider normal and tailor their reverse DNS
so as not to offend your aesthetic sense. It is frustrating when other
people do things differently, my deepest sympathies.
Also if you have ever used a BSD sys
This is probably worse then hexadecimal PTR records :). No traceroute
actually convert punycode, so why bother? As it usually intended
audience already know how to read English letters.
On 14/04/15 17:00, Pavel Odintsov wrote:
> What about IDN encoded PTR records? I sure it's nice idea and I will
y would probably declare:
>>>
>>> "Worst Naming Convention Ever"
>>>
>>> Chuck
>>>
>>> -Original Message-
>>> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Colin Johnston
>>> Sent: Tuesday, April
--
>>> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Colin Johnston
>>> Sent: Tuesday, April 14, 2015 9:27 AM
>>> To: Nikolay Shopik
>>> Cc:
>>> Subject: Re: macomnet weird dns record
>>>
>>> Because looks strange especially if
* col...@gt86car.org.uk (Colin Johnston) [Tue 14 Apr 2015, 16:05 CEST]:
Be that as it may, why not use either normal decimal numbers or
normal characters to show what a normal person would understand
instead of having to convert the shown output ?
I actually thought it was quite clever and the
wrote:
>> Comic Book Guy would probably declare:
>>
>> "Worst Naming Convention Ever"
>>
>> Chuck
>>
>> -Original Message-
>> From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Colin Johnston
>> Sent: Tuesday, April
lin Johnston
>> Sent: Tuesday, April 14, 2015 9:27 AM
>> To: Nikolay Shopik
>> Cc:
>> Subject: Re: macomnet weird dns record
>>
>> Because looks strange especially if the traffic is 100% bad Best practice
>> says avoid such info in records as does not aid debug
gt; From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Colin Johnston
> Sent: Tuesday, April 14, 2015 9:27 AM
> To: Nikolay Shopik
> Cc:
> Subject: Re: macomnet weird dns record
>
> Because looks strange especially if the traffic is 100% bad Best practice
> says avoid such
Get real, why make is hard for others to debug abuse issues, another reason why
blocks in place as no technical cooperation.
Colin
> On 14 Apr 2015, at 14:48, Nikolay Shopik wrote:
>
> Then best practice, that naming should be helpful for owners of network
> in first place and only afterwards
Then best practice, that naming should be helpful for owners of network
in first place and only afterwards everyone else.
On 14/04/15 16:26, Colin Johnston wrote:
> Because looks strange especially if the traffic is 100% bad
> Best practice says avoid such info in records as does not aid debug si
On Tue, Apr 14, 2015 at 02:26:48PM +0100,
Colin Johnston wrote
a message of 19 lines which said:
> Best practice says avoid such info in records as does not aid debug
> since mix of dec and hex
No. Pure imagination on your side. There is no such "best
practice". And it's not hex or dec, it is
Comic Book Guy would probably declare:
"Worst Naming Convention Ever"
Chuck
-Original Message-
From: NANOG [mailto:nanog-boun...@nanog.org] On Behalf Of Colin Johnston
Sent: Tuesday, April 14, 2015 9:27 AM
To: Nikolay Shopik
Cc:
Subject: Re: macomnet weird dns record
Bec
Because looks strange especially if the traffic is 100% bad
Best practice says avoid such info in records as does not aid debug since mix
of dec and hex
Colin
> On 14 Apr 2015, at 14:09, Nikolay Shopik wrote:
>
> How its weird? All these chars allowed in DNS records.
>
> On 14/04/15 15:36,
On Tue, Apr 14, 2015 at 04:09:42PM +0300,
Nikolay Shopik wrote
a message of 10 lines which said:
> How its weird? All these chars allowed in DNS records.
And they probably encode the netmask, which may be useful.
How its weird? All these chars allowed in DNS records.
On 14/04/15 15:36, Colin Johnston wrote:
> never saw hex in host dns records before.
> host-242.strgz.87.118.199.240.0xfff0.macomnet.net
>
> range is blocked non the less since bad traffic from Russia network ranges.
>
> Colin
>
never saw hex in host dns records before.
host-242.strgz.87.118.199.240.0xfff0.macomnet.net
range is blocked non the less since bad traffic from Russia network ranges.
Colin
30 matches
Mail list logo
