<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 href="http://bdr01-vlan309.syd01.nsw.domain.net">bdr01-vlan309.syd01.nsw.domain.net</a>. or bdr01-gi4-117, or <a 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 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"><br>
-----Original Message-----<br>
From: AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Daniel<br>
Sent: Thursday, 4 December 2014 3:37 PM<br>
To: 'Jacob Kino'; <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
Subject: Re: [AusNOG] Reverse DNS Recommendations<br>
<br>
</span><div class="HOEnZb"><div class="h5">Not sure if it helps or not, but we recently went through the same process<br>
<br>
How we tackled it, was we setup 4 VM's around the country, all on separate subnets, aka for example of the following<br>
<br>
10.1.1.251<br>
10.1.2.251<br>
10.1.3.251<br>
10.1.4.251<br>
<br>
Which is RFC complient<br>
<br>
We used powerdns/poweradmin to control all of this<br>
<br>
Hope this helps in a round about way :D<br>
<br>
<br>
D.<br>
<br>
-----Original Message-----<br>
From: AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net">ausnog-bounces@lists.ausnog.net</a>] On Behalf Of Jacob Kino<br>
Sent: Thursday, 4 December 2014 3:28 PM<br>
To: <a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
Subject: [AusNOG] Reverse DNS Recommendations<br>
<br>
Hi All,<br>
<br>
We're in the process of doing some spring cleaning around our network and looking to implement more consistent and meaningful reverse DNS.<br>
<br>
I had a look back through the archives and didn't find anything useful in terms of either an RFC (wouldn't have really expected one) or references to guidelines/a standard.<br>
<br>
We've performed some analysis on what others do, but due to the design of our network there are some cases where we aren't quite sure what's most appropriate.<br>
<br>
Specifically, VLANs seem to present a bit of a challenge as well as links between virtualized firewall instances. I'm trying to come up with a conceptual framework that makes general sense so we can develop something from that, if such a thing exists.<br>
<br>
If anyone has tackled this issue and has guidance they can share, that would be excellent - happy for on-list and off-list replies.<br>
<br>
Cheers,<br>
<br>
Jacob | Interconnekt<br>
<br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br>
_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div><span class="im HOEnZb">Charles Sturt University<br>
<br>
| ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ONTARIO | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA |<br>
<br>
LEGAL NOTICE<br>
This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.<br>
<br>
Charles Sturt University in Australia <a href="http://www.csu.edu.au" target="_blank">http://www.csu.edu.au</a> The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Numbers: 00005F (NSW), 01947G (VIC), 02960B (ACT)). TEQSA Provider Number: PV12018<br>
<br>
Charles Sturt University in Ontario <a href="http://www.charlessturt.ca" target="_blank">http://www.charlessturt.ca</a> 860 Harrington Court, Burlington Ontario Canada L7N 3N4 Registration: <a href="http://www.peqab.ca" target="_blank">www.peqab.ca</a><br>
<br>
Consider the environment before printing this email.<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">
<p>Damien Gardner Jnr<br>VK2TDG. Dip EE. GradIEAust<br><a href="mailto:rendrag@rendrag.net" target="_blank">rendrag@rendrag.net</a> - <span><a href="http://www.rendrag.net/" target="_blank">http://www.rendrag.net/</a><u><br></u></span>--<br>We rode on the winds of the rising storm,<br> We ran to the sounds of thunder.<br>We danced among the lightning bolts,<br> and tore the world asunder</p></div></div>
</div>