[AusNOG] Reverse DNS Recommendations

[Tim Raphael]

Similar to an idea I scripted up for a previous employer - walk a device with SNMP and grab all interfaces with public addresses on them.
Use the interface type / speed combined with unit / sub interface number and construct something like this:

<type> - <int-id> - <unit/vlan-id> . <device-hostname> . <state/region-code> . <TLDR>

E.g:

xe1-203. <http://xe1-203.persgtrt01.wa.myisp.net/>persgtrt01.wa.myisp.net.au <http://persgtrt01.wa.myisp.net.au/> or ae2-144. <http://ae2-144.sydparst01.nsw.myisp.net/>sydparst01.nsw.myisp.net.au <http://sydparst01.nsw.myisp.net.au/> 

As you can have both IPv4 and IPv6 addresses on the same interface, you can use the unit / vlan ID irrespective of the addressing type.

Run this once a week and have it push the changes into pdns / bind etc and viola :p

- Tim


> On 4 Dec 2014, at 2:05 pm, Nick Pratley <nick.pratley at serversaustralia.com.au> wrote:
> 
> +1
> 
> My Proof of Concept code parses the latest configuration file saved by rancid for each switch & router, dumping into a Power DNS cluster.
> 
> The downside to the approach I took, was realising that Observium saves all the information (IPs on Layer 3 ports and vlan interconnects), and I could have just pulled all the data for this project from that DB.
> 
> I am also happy to answer questions / help with examples of the code parsing the config files if needed.
> 
> Just on this note, there is a really awesome python tool I found. Takes the entire text config and converts to JSON.
> https://github.com/knipknap/Gelatin <https://github.com/knipknap/Gelatin>
> 
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20141204/f6435cc1/attachment.html>