Re: non-24 bit subnets

2010-10-07 Thread Barry Finkel
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; 30

Re: non-24 bit subnets

2010-10-07 Thread Gordon A. Lang
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 own

non-24 bit subnets

2010-10-06 Thread Alex McKenzie
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greetings, I'm setting up a new DNS server for internal use in the two departments I support. Up until very recently, all our subnets have had 24 bit masks, which has made configuring bind very easy. However, we now have three sizes, and may have

Re: non-24 bit subnets

2010-10-06 Thread Matt Baxter
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

Re: non-24 bit subnets

2010-10-06 Thread Alex McKenzie
-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

Re: non-24 bit subnets

2010-10-06 Thread Jay Ford
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

Re: non-24 bit subnets

2010-10-06 Thread David Miller
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

Re: non-24 bit subnets

2010-10-06 Thread Alex McKenzie
-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 problem

Re: non-24 bit subnets

2010-10-06 Thread Jay Ford
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

Re: non-24 bit subnets

2010-10-06 Thread Alex McKenzie
-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 lookup

Re: non-24 bit subnets

2010-10-06 Thread Mark Andrews
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 can they be