|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Domain names for ISP infrastructure links
>> So how do we name internal links in a way that is usefull for
>> all operators, and conforms to the A-Z 0-9 and "-" and can
>> be proposed as an RFC?
>
>Well, here's what I suggested to UUNET and Genuity, which they mostly did:
[...]
> [<iface>.]<router>.<pop>.<toplev>
>
>where
>
> <iface> is something like <type><slot>[-<port>], i.e.,
> fddi0 -> f0 (no port number)
> ethernet2/3 -> e2-3
> hssi4.21 -> h4-21 (subinterface 21)
> note that <iface> is optional since the router's loopback
> interface address (for IBGP) will just be the router's name.
>
> <router> is something like "CR2".
>
> <pop> is something like "DCA1".
>
> <toplev> is something like "alter.net".
I got tired of trying to fix this problem one interface at a time
and finally wrote a script that digests a Cisco config file and
produces both an error report and the named db files. We use a slightly
different convention, but the script is easy to modify.
% cat clv1.oar.net | ./ifdns -foar.cfg -e
Reverse lookup problem report
IP Address Current Hostname Correct Hostname
------------------------------------------------------------------------------
131.187.68.5 csp-ccf.oar.net clv1-sl9-5.cle.oar.net
199.18.19.5 clv1-lo0.cleveland.oar.net clv1-lo0.cle.oar.net
199.18.21.1 clv1-e0.oar.net clv1-eth0-0.cle.oar.net
...
Forward lookup problem report
Hostname Current IP Address Correct IP Addrses
------------------------------------------------------------------------------
clv1-sl9-5.cle.oar.net *** 131.187.68.5
clv1-lo0.cle.oar.net *** 199.18.19.5
clv1-eth0-0.cle.oar.net *** 199.18.21.1
..
ftp://ftp.net.ohio-state.edu/users/maf/priv/ifdns and oar.cfg or osu.cfg
--
mark
- - - - - - - - - - - - - - - - -
|