Re: [AFMUG] infrastructure PTR naming conventions

[Jesse DuPont]

I pretty much stick to these: dyn-192-168-1-1.celerityinternet.com static-192-168-1-1.celerityinternet.com <real-host-name>.celerityinernet.com I know it's forward notation, but I prefer to keep them simple. Also valuable in some cases is setting a longer TTL value for your non-dynamic-use PTR records (like 86400 or 43200). It avoids you having to change them later when someone with a static IP gets black listed on a DUL email server list. Also, right or wrong, I use loose geographical naming conventions (based on CLLI naming convention) for PTR records for L3 interfaces so traceroutes are more intuitive. So, one of our towers is called SDPB and it's in Spearfish so I might use "sprf-sdpb-ccr-eth1.celerityinternet.com". If nothing else, as the network grows, it's helpful internally. Jesse DuPont Network Architect email: jesse.dup...@celeritycorp.net Celerity Networks LLC Celerity Broadband LLC Like us! facebook.com/celeritynetworksllc Like us! facebook.com/celeritybroadband On 8/24/16 8:11 AM, That One Guy /sarcasm wrote: 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.