[179460] 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 (Chuck Church)
Tue Apr 14 09:48:13 2015

X-Original-To: nanog@nanog.org
From: "Chuck Church" <chuckchurch@gmail.com>
To: "'Colin Johnston'" <colinj@gt86car.org.uk>,
 "'Nikolay Shopik'" <shopik@inblock.ru>
In-Reply-To: <B23E9C8B-2E95-46B1-9401-218B7B914A80@gt86car.org.uk>
Date: Tue, 14 Apr 2015 09:45:00 -0400
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org

Comic Book Guy would probably declare:

"Worst Naming Convention Ever"

Chuck

-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Colin Johnston
Sent: Tuesday, April 14, 2015 9:27 AM
To: Nikolay Shopik
Cc: <nanog@nanog.org>
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 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