<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I wrote something very similar to what Damien said (completely
automating record generation using PowerDNS).<br>
<br>
I used snmp with 1.3.6.1.2.1.4.20.1.2 (
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
ipAdEntIfIndex) and 1.3.6.1.2.1.31.1.1.1.1 (ifName) combined with
some logic bound to each device and some rules as to how your arpa
files are generated (eg: 10.1.2.0/24's records would be sitting in
2.1.10.in-addr.arpa's zone), and away you go.<br>
<br>
In regards to IPv6 and auto generating records was slightly
challenging as I haven't found a way to do it using snmp yet (please
ping me off-list if you know an easier way), so I just parse the
configuration files which also works fine, but not as efficient as
I'd want it to be. The arpa records are handled differently too (not
1:1).<br>
<br>
With however you name the records, I guess it's how you like it (or
how your companies naming convention is).<br>
<br>
Happy to give some examples off-list.<br>
<br>
Regards,<br>
Matt.<br>
<br>
<div class="moz-cite-prefix">On 4/12/2014 16:13, Damien Gardner Jnr
wrote:<br>
</div>
<blockquote
cite="mid:CAPrfDLXGX73WHyoPEvUtEyOJ8GN5tZ-LbJveQ0fSO467AFBHew@mail.gmail.com"
type="cite">
<div dir="ltr">Couple of jobs ago, we were generating our reverse
DNS via a few mysql stored procedures behind powerdns, which
directly queried our network management portal. Was extremely
cool, though was finished only a few week before the company got
sold and the new owners nuked everything. Format generated was
devicename-interface.datacenter.state.domainname.
<div><br>
</div>
<div>i.e. <a moz-do-not-send="true"
href="http://bdr01-vlan309.syd01.nsw.domain.net">bdr01-vlan309.syd01.nsw.domain.net</a>.
or bdr01-gi4-117, or <a moz-do-not-send="true"
href="http://sw12-vlan174.lax01.ca.domain.net">sw12-vlan174.lax01.ca.domain.net</a>.
Probably could have done with country code in there as well
but it was still very nicely readable in traceroutes, which is
pretty much what this is all for, right? ;)</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On 4 December 2014 at 15:58, Beeson,
Ayden <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ABeeson@csu.edu.au" target="_blank">ABeeson@csu.edu.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I think
Jacob is more referring to what to put for the reverse PTR's
for devices that don't have clear single IP A/AAAA/PTR
records, such as routers, vlans etc.<br>
<br>
What we have done here (or are doing, it's still in flux so
I'm open to ANY other better suggestions) is to base the PTR
on the IP / subnet it is serving.<br>
<br>
We have a single /16 IPv4 which for the most part is divided
into /24's, so we are planning to basically reflect the IP
directly.<br>
<br>
I.e. for 137.166.140.254 (the router for my subnet) we will
call it gw-140 and insert relevant A and PTR records for
this, for those with HSRP etc you can add -a / -b etc as
well.<br>
<br>
I have adapted this for IPv6 as well for our /32, so for
example 2405:2d00:301:2000::1 (my router again) becomes
gw-301-2000<br>
<br>
It's not perfect, but at least it's predictable and
repeatable. For the more specific subnets such as P2P /30,
/31, /126 or /127's I haven't come up with a solid plan yet
other than to scale this out to a longer name, or
potentially go with a more descriptive name.<br>
<br>
It also wouldn't work if you had a whole bunch of separate
network ranges, at least not in a small and easy fashion.<br>
<br>
Thanks,<br>
Ayden Beeson<br>
<span class="im HOEnZb"></span><br>
</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>