Delegating class C's

Joseph S D Yao jsdy at cospo.osis.gov
Tue May 15 22:14:59 UTC 2001


On Tue, May 15, 2001 at 10:14:56AM -0700, Robert Gahl wrote:
> We run a non-routeable class C in our office (192.168.254). We are creating 
> other 192.168.x "sub-domains" for labs and such, but we need to delegate 
> not just the forward but the reverse to these DNS servers as well. Rather 
> than go into, say, db.192.168.0, and list 255 entries of (looking at page 
> 217 of the book):
> 
> x.0.168.192.in-addr.arpa.       IN CNAME        x.0-255.0.168.192.in-addr.arpa.
> 
> with
> 
> 0-255.0.168.192.in-addr.arpa.   IN NS           ns1.eng.fireclick.com.
> 
> is there a short hand that says, give the entire class C to the machine 
> ns1.eng.fireclick.com? Or, do I just have to pre-delegate each IP within 
> the master DNS server's db.192.168.254 zone file?

You are using the special-case RFC2317 stuff where you don't need to.

Reverse DNS domains are EXACTLY THE SAME as any other domains.  If I am
a server for "168.192.in-addr.arpa.", then my zone.192.168 file might
contain the following to delegate its subdomains, exactly the same as
any subdomains the world over are delegated:

$TTL	...
@	SOA	...
	NS	thishost.domain.

1	NS	ns1.eng.fireclick.com.
...
42	NS	joes.barandgrill.com.
...

On ns1.eng.fireclick.com, of course, the zone.192.168.1 zone file MUST
repeat the NS statement for itself - exactly the same as any other
subdomain in the world:

$TTL	...
@	SOA	...
	NS	ns1.eng.fireclick.com.

0	PTR	network-0.eng.fireclick.com.
1	PTR	host1.eng.fireclick.com.
...
42	PTR	lategreatdouglasa.eng.fireclick.com.
...

If there is a pattern, you may be able to use the $GENERATE macro.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
OSIS Center Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.


More information about the bind-users mailing list