not reachable from the outside
From: Af [mailto:af-boun...@afmug.com <mailto:af-boun...@afmug.com> ] On Behalf
Of That One Guy /sarcasm
Sent: August 24, 2016 10:12 AM
To: af@afmug.com <mailto:af@afmug.com>
Subject: [AFMUG] infrastructure PTR naming conventions
I know this is
t; /sarcasm
> *Sent:* August 24, 2016 10:12 AM
> *To:* af@afmug.com
> *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 u
] On Behalf Of That One Guy /sarcasm
Sent: August 24, 2016 10:12 AM
To: af@afmug.com
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
On the server authoritative for the [inverse ip].in-addr.arpa zone.
-- Original Message --
From: "That One Guy /sarcasm"
To: "af@afmug.com"
Sent: 8/24/2016 8:50:55 PM
Subject: Re: [AFMUG] infrastructure PTR naming conventions
Im lost.
We have two production autho
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 wrote:
> For infrastructure:
>
> vl[A]-[B][
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
I agree with Jesse. You want enough data to find things out without
excessive digging, but you don't need to document the world.
Place-Device-Interface is plenty for traceroutes, and dyn/static is
enough for pools.
On 8/24/2016 9:35 AM, That One Guy /sarcasm wrote:
thats the space im talking a
thats the space im talking about, infrastructure like
---.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 in it
On Wed, Aug 24
I pretty much stick to these:
dyn-192-168-1-1.celerityinternet.com
static-192-168-1-1.celerityinternet.com
.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
router.domain.com
On Wed, Aug 24, 2016 at 10:11 AM, That One Guy /sarcasm <
thatoneguyst...@gmail.com> 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 conv
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 p
11 matches
Mail list logo
