[157454] in North American Network Operators' Group
Re: Semi-automated L3 interface DNS records
daemon@ATHENA.MIT.EDU (Joe Abley)
Mon Oct 22 22:18:41 2012
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <7EF4A8B03B0A3A44858C8B42E0DB236A0121BC431C41@PHX-52N-EXM04A.lcc.usairways.com>
Date: Mon, 22 Oct 2012 21:18:20 -0500
To: "Pedersen, Sean" <Sean.Pedersen@usairways.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 2012-10-18, at 14:57, "Pedersen, Sean" <Sean.Pedersen@usairways.com> =
wrote:
> 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 Layer 3 interfaces on routers and switches?
http://www.nanog.org/meetings/nanog26/presentations/stephen.pdf
ftp://ftp.isc.org/isc/toolmakers/
> We'd like to move toward this practice to help with troubleshooting =
and IPAM, but it's not feasible to do it manually. At a minimum, I was =
mulling over 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 be better than doing that portion of the =
work manually. Cleaning up dead entries would be another issue.
AS6461 once had the bulk of its reverse DNS auto-generated from awk =
scripts. It's the only way to travel.
Joe=
