[179462] in North American Network Operators' Group
Re: macomnet weird dns record
daemon@ATHENA.MIT.EDU (Colin Johnston)
Tue Apr 14 09:54:36 2015
X-Original-To: nanog@nanog.org
From: Colin Johnston <colinj@gt86car.org.uk>
In-Reply-To: <552D1AC8.7010108@inblock.ru>
Date: Tue, 14 Apr 2015 14:51:24 +0100
To: Nikolay Shopik <shopik@inblock.ru>
Cc: "<nanog@nanog.org>" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
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 <shopik@inblock.ru> wrote:
>=20
> Then best practice, that naming should be helpful for owners of =
network
> in first place and only afterwards everyone else.
>=20
> On 14/04/15 16:26, Colin Johnston wrote:
>> Because looks strange especially if the traffic is 100% bad=20
>> Best practice says avoid such info in records as does not aid debug =
since mix of dec and hex=20
>>=20
>> Colin
>>=20
>>> On 14 Apr 2015, at 14:09, Nikolay Shopik <shopik@inblock.ru> wrote:
>>>=20
>>> How its weird? All these chars allowed in DNS records.
>>>=20
>>> On 14/04/15 15:36, Colin Johnston wrote:
>>>> never saw hex in host dns records before.
>>>> host-242.strgz.87.118.199.240.0xfffffff0.macomnet.net
>>>>=20
>>>> range is blocked non the less since bad traffic from Russia network =
ranges.
>>>>=20
>>>> Colin
>>>>=20
>>=20
