I've seen people use both Cisco and Juniper abbreviations for interface capacities in a hostname/reverse DNS. Even both, in the same network.
For those who are using mikrotik and want to do "proper" professional reverse DNS for routed backbone interfaces, I would strongly encourage you to use cisco or juniper abbreviations, because the NOCs of other ISPs can understand it easily when troubleshooting. Such as: fa (FastEthernet) for 100Mbps, gi (GigabitEthernet) for 1000, te (TenGigabitEthernet). po (portchannel) Or the Juniper equivalents... ge (gigabit), xe (ten gig), ae (aggregated ethernet, the junos version of a portchannel) On Fri, Dec 2, 2016 at 11:30 AM, Paul Stewart <[email protected]> wrote: > Kind of funny - I’m working on updated naming conventions with my team at > $$$job …. > > In former job, for network devices it was: > > xe-10-0-0-1 (10G interface, slot/proc/port, vlan # if appropriate) > dis1/core1/acc1 (distribution/core/access device #1) > toronto3 (city location #) > domain name > > So xe-10-0-0-1.core3.toronto5.domain.com for example > > In current process, we want to elaborate on our current design to include > the role, the priority/critical nature of the port, where it connects etc > this way we can build automation around those names in other systems (ie. > network monitoring) > > On Dec 2, 2016, at 1:58 PM, Eric Kuhnke <[email protected]> wrote: > > 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. >> > > >
