Of note, v13.eth1.locID.tld.net is much different than v13-eth1-locID.tld.net when it comes to dns. If you use periods in your names, you're actually creating subzones, which can greatly complicate your life and your dns. Unless you have a very strong reason to use sub zones, like you run dns in different states with different resolvers, or AD is in your main tld (like you should be), then stick to hyphens.
On Aug 27, 2016 8:43 AM, "Paul Stewart" <[email protected]> wrote: > All of our RFC1918 space is for management so they all follow > device.man.loc.domain.com > > > > Device – device name > > Man – management > > Loc – three letter location POP code > > Domain.com – our domain > > > > These internal zones are not reachable from the outside > > > > *From:* Af [mailto:[email protected]] *On Behalf Of *That One Guy > /sarcasm > *Sent:* August 24, 2016 10:12 AM > *To:* [email protected] > *Subject:* [AFMUG] infrastructure PTR naming conventions > > > > I know this is alot like asking which mail server is best or which cable > to use. Im putting up a DNS server with our rfc1918 space thats in use on > it. Ive been reading a ton of conventions people use, some granular, some > vague. > > anybody care to share some examples? > > > > -- > > If you only see yourself as part of the team but you don't see your team > as part of yourself you have already failed as part of the team. >
