What I've found works best (especially for NMS like OpenView, Nagios, etc) is to setup a loopback interface. Setup DNS with a A record for the loopback interface as the "One True Name(tm)". Then setup all reverse PTR records for all interfaces to be the same as the forward for the loopback. Then if I need to address individual interfaces I setup a forward A record for those, but leave the PTR going back to the loopback name.
---- Matthew Huff | One Manhattanville Rd OTA Management LLC | Purchase, NY 10577 http://www.ox.com | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139 > -----Original Message----- > From: cisco-nsp-boun...@puck.nether.net > [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Andrew > Miehs > Sent: Thursday, September 02, 2010 1:05 PM > To: cisco...@secureobscure.com > Cc: cisco-nsp@puck.nether.net > Subject: Re: [c-nsp] DNS Naming conventions for Switches > > Thanks for both the answers so far. > > My biggest issue however is with the management/ loopback interface. > > Does everyone just use a cname for the switch/ router name - and the reverse > lookup for this address is then the 'real' interface name? > > Thanks > > Andrew > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
