[AusNOG] Reverse DNS Recommendations

Thu Dec 4 16:00:35 EST 2014

Think alike :p

We do similar, 103.18.205.0/24 we call the gateway
"gw-205.nsw.au.glovine.com.au"

IPv6 is very similar, 2406:8900:10::/48 we call the gateway
"gw-10.nsw.au.glovine.com.au"

We might change this in the near future as you can see numbers will start
clashing soon if we get upto 2406:8900:205::/48 :d

D.

-----Original Message-----
From: Beeson, Ayden [mailto:ABeeson at csu.edu.au] 
Sent: Thursday, 4 December 2014 3:58 PM
To: 'Daniel'; 'Jacob Kino'; 'AusNOG at lists.ausnog.net'
Subject: RE: [AusNOG] Reverse DNS Recommendations

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.

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.

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.

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.

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

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.

It also wouldn't work if you had a whole bunch of separate network ranges,
at least not in a small and easy fashion.

Thanks,
Ayden Beeson

-----Original Message-----
From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Daniel
Sent: Thursday, 4 December 2014 3:37 PM
To: 'Jacob Kino'; AusNOG at lists.ausnog.net
Subject: Re: [AusNOG] Reverse DNS Recommendations

Not sure if it helps or not, but we recently went through the same process

How we tackled it, was we setup 4 VM's around the country, all on separate
subnets, aka for example of the following

10.1.1.251
10.1.2.251
10.1.3.251
10.1.4.251

Which is RFC complient

We used powerdns/poweradmin to control all of this

Hope this helps in a round about way :D

D.

-----Original Message-----
From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Jacob
Kino
Sent: Thursday, 4 December 2014 3:28 PM
To: AusNOG at lists.ausnog.net
Subject: [AusNOG] Reverse DNS Recommendations

Hi All,

We're in the process of doing some spring cleaning around our network and
looking to implement more consistent and meaningful reverse DNS.

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.

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.

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.

If anyone has tackled this issue and has guidance they can share, that would
be excellent - happy for on-list and off-list replies.

Cheers,

Jacob | Interconnekt

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

_______________________________________________
AusNOG mailing list
AusNOG at lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog
Charles Sturt University

| ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE |
ONTARIO | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA |

LEGAL NOTICE
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.

Charles Sturt University in Australia  http://www.csu.edu.au  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

Charles Sturt University in Ontario  http://www.charlessturt.ca 860
Harrington Court, Burlington Ontario Canada L7N 3N4  Registration:
www.peqab.ca

Consider the environment before printing this email.