On the server authoritative for the [inverse ip].in-addr.arpa zone.
------ Original Message ------
From: "That One Guy /sarcasm" <[email protected]>
To: "[email protected]" <[email protected]>
Sent: 8/24/2016 8:50:55 PM
Subject: Re: [AFMUG] infrastructure PTR naming conventions
Im lost.
We have two production authoritative DNS servers for our domains and
allocation
Im building the first of two recursive servers for our customers, and
office
where would I actually put these records?
On Wed, Aug 24, 2016 at 9:42 AM, Josh Baird <[email protected]>
wrote:
For infrastructure:
vl[A]-[B][C].[D].net.domain.com
A = vlan-id
B = device type (irtr, artr, cr, etc)
C = device index (0, 1, 2, etc)
D = location id
Example:
vl7-artr1.dan100.net.domain.com
(vlan 7 interface of "artr1" at "dan100")
For customer/dymamic pools, we just do something simple like:
ip-1.2.3.4.cust.domain.com
Josh
On Wed, Aug 24, 2016 at 10:35 AM, That One Guy /sarcasm
<[email protected]> wrote:
thats the space im talking about, infrastructure like
<speed>-<portID>-<localsite>-<remotesite>.domain.com for traceroutes
(remote site matches my ip documentation and will help catch a
forgotten update if we move a backhaul)
i guess alot of it is how much is enough, not enough, and too much, I
assume i dont want <username/password> in it
On Wed, Aug 24, 2016 at 9:27 AM, Jesse DuPont
<[email protected]> wrote:
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: [email protected]
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.
--
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.
--
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.
