Properly done DNS systems can deal with much longer hostnames than that, but from a human readability and usability perspective, I would use hyphens to separate things a bit. And do it hierarchically rather than one flat hostname.domain.
Look at the reverse DNS entries for the 1, 10, 40 and 100Gb interfaces on major ISP backbone routers in a traceroute for examples. On Fri, Dec 2, 2016 at 10:49 AM, That One Guy /sarcasm < [email protected]> wrote: > beating this horse again. > Is there any component of DNS that would be problematic with a 16 > character name? > > Im going with VLAN ID, Port type and number, Device type and number, > location > all are 4 characters > > VL01GE04RT01CBN0.domain > > This is > VLAN ID 1 default (will remove letters if VLAN goes beyond 99 or 999) > Gigabit Ethernet > Port number 1 > Router 1 > at CBN > > it just looks really long and cumbersome and im afraid one day some > standard im unaware of will hammer me, like a proper ICANN API instruction > for some newly required function will kill everyone in the room with lazes > if the entry exceeds 9 characters > > -- > If you only see yourself as part of the team but you don't see your team > as part of yourself you have already failed as part of the team. >
