In article ,
David Miller wrote:
> You can have a different TTL for each and every record, if you like, in
> the same zone file with no includes (the $TTL directive can appear
> multiple times).
>
> e.g. :
>
> $TTL 300; 5 mins
> *PTRhost-no-spec.example.com.
> $TTL 3600; 1 ho
As long as all of the in-addr.arpa data is administered on the same
master(s), then just use an "8-bit zone" i.e. 10.in-addr.arpa.
Everything within the 10 dot range all fits into a single zone.
The $INCLUDE directive gives you some independent flexibility,
and each record can (should) have its ow
>
>You can have a different TTL for each and every record, if you like, in
>the same zone file with no includes (the $TTL directive can appear
>multiple times).
>
>e.g. :
>
>$TTL 300; 5 mins
>*PTRhost-no-spec.example.com.
>$TTL 3600; 1 hour
>17 PTR mail.example.com.
>$TTL 1800
In message <4cacdf3c.9040...@chem.umass.edu>, Alex McKenzie writes:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> Jay Ford wrote:
> > On Wed, 6 Oct 2010, Alex McKenzie wrote:
> >> Out of curiosity: what if it's a /16 or /8 network? Do those also get
> >> built as 24 bit files, or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jay Ford wrote:
> On Wed, 6 Oct 2010, Alex McKenzie wrote:
>> Out of curiosity: what if it's a /16 or /8 network? Do those also get
>> built as 24 bit files, or can they be built differently? I seem to
>> recall seeing an option for a reverse look
On Wed, 6 Oct 2010, Alex McKenzie wrote:
Out of curiosity: what if it's a /16 or /8 network? Do those also get
built as 24 bit files, or can they be built differently? I seem to
recall seeing an option for a reverse lookup file with hosts declared as:
x.y PTR host.domain.tld.
Does th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Miller wrote:
> On 10/6/2010 3:21 PM, Jay Ford wrote:
>> On Wed, 6 Oct 2010, Alex McKenzie wrote:
>>> Unfortunately, we do have need -- or at least a use -- to have smaller
>>> subnets in multiple files, but without delegating authority. The
On 10/6/2010 3:21 PM, Jay Ford wrote:
On Wed, 6 Oct 2010, Alex McKenzie wrote:
Unfortunately, we do have need -- or at least a use -- to have smaller
subnets in multiple files, but without delegating authority. The
problem is that some of those small subnets should have a shorter TTL,
or other
On Wed, 6 Oct 2010, Alex McKenzie wrote:
Unfortunately, we do have need -- or at least a use -- to have smaller
subnets in multiple files, but without delegating authority. The
problem is that some of those small subnets should have a shorter TTL,
or other settings changed. If there's a way to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the quick reply, Matt.
Unfortunately, we do have need -- or at least a use -- to have smaller
subnets in multiple files, but without delegating authority. The
problem is that some of those small subnets should have a shorter TTL,
or other
For larger subnets just use multiple zones as necessary.
For 10.20.30.0/23 you have 30.20.10.in-addr.arpa and 31.20.10.in-addr.arpa.
For smaller than a /24 look at RFC 2317. That's only necessary if you want to
delegate authority to a different DNS server. If you have multiple networks in
a
11 matches
Mail list logo