[157437] in North American Network Operators' Group
RE: Semi-automated L3 interface DNS records
daemon@ATHENA.MIT.EDU (Pedersen, Sean)
Mon Oct 22 11:07:25 2012
From: "Pedersen, Sean" <Sean.Pedersen@usairways.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Mon, 22 Oct 2012 08:06:29 -0700
In-Reply-To: <7EF4A8B03B0A3A44858C8B42E0DB236A0121BC431C41@PHX-52N-EXM04A.lcc.usairways.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Thanks to everyone that responded. Based on the information from this list =
and several other areas I posted the same question, it seems like a feasibl=
e goal.=20
If anyone has any ideas on how to either reduce my sleeping requirements or=
extend the number of hours in a day so that I can actually implement this,=
I would love to hear from you. :-P
-----Original Message-----
From: Pedersen, Sean [mailto:Sean.Pedersen@usairways.com]=20
Sent: Thursday, October 18, 2012 12:57 PM
To: nanog@nanog.org
Subject: Semi-automated L3 interface DNS records
Does anyone out there have any experience with a script, tool or appliance =
that would help manage the creation and maintenance of DNS records for Laye=
r 3 interfaces on routers and switches?
We'd like to move toward this practice to help with troubleshooting and IPA=
M, but it's not feasible to do it manually. At a minimum, I was mulling ove=
r the idea of writing a script that would poll a device via SNMP to obtain =
interface information, parse it, compare the results to DNS, then generate =
a report if it found a miss. It wouldn't be fully-automated, but it would b=
e better than doing that portion of the work manually. Cleaning up dead ent=
ries would be another issue.
