[179461] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: macomnet weird dns record

daemon@ATHENA.MIT.EDU (Nikolay Shopik)
Tue Apr 14 09:51:20 2015

X-Original-To: nanog@nanog.org
Date: Tue, 14 Apr 2015 16:48:56 +0300
From: Nikolay Shopik <shopik@inblock.ru>
To: Colin Johnston <colinj@gt86car.org.uk>
In-Reply-To: <B23E9C8B-2E95-46B1-9401-218B7B914A80@gt86car.org.uk>
Cc: "<nanog@nanog.org>" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

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 since mix of dec and hex 
> 
> Colin
> 
>> On 14 Apr 2015, at 14:09, Nikolay Shopik <shopik@inblock.ru> wrote:
>>
>> 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.0xfffffff0.macomnet.net
>>>
>>> range is blocked non the less since bad traffic from Russia network ranges.
>>>
>>> Colin
>>>
> 

home help back first fref pref prev next nref lref last post