Reverse for a /23

Mark.Andrews at iengines.com Mark.Andrews at iengines.com
Tue Dec 21 23:40:28 UTC 1999


> 
> O.K... I haven't been able to get ahold of a up to date Cricket book...
> (mine is revision 1) and I have read RFC2317... but I am still having
> nothing but problems doing reverse for a supernet... in this case, a /23.
> 
> I am feeling really stupid and need someone to explain this to me step by
> step... ;-)
> 
> I am running BIND 8.1.2 and lets say I am trying to set up reverse for
> 192.168.218.0/23 (192.168.218.0/24 and 192.168.219.0/24).
> 
> I put in my named.conf:

	Just create 218.168.192.in-addr.arpa and 219.168.192.in-addr.arpa

	You don't need to apply the techniques in RFC 2317 as they apply
	to /25 - /32.

	Mark

> 
> zone "218/23.168.192.in-addr.arpa" {
> 	type master;
> 	file "db.192.168.218";
> };
> 
> And I put in db.192.168.218:
> 
> 218/23.251.204.in-addr.arpa.	IN SOA ns.our.net someone.our.net (
> 				1999121701	;Serial
> 				10800		;Refresh after 3 hours
> 				3600		;Retry after 1 hour
> 				604800		;Expire after 1 week
> 				86400	)	;Minimum TTL of 1 day
> 
> 218/23.251.204.in-addr.arpa.	IN NS	ns.our.net.
> 218/23.251.204.in-addr.arpa.	IN NS	ns2.our.net.
> 
> 1.218.251.204.in-addr.arpa.	IN PTR	blah.our.net.
> 129.218.251.204.in-addr.arpa.	IN PTR	blah2.our.net.
> 1.219.251.204.in-addr.arpa.	IN PTR	blah3.our.net.
> 22.219.251.204.in-addr.arpa.	IN PTR	blah4.our.net.
> 
> When I HUP BIND, it just gets all upset and drops the whole zone.
> 
> Maybe I've read RFC2317 totally wrong, but the bottom line is I'm confused
> over the whole situation.
> 
> 					----Steve
> Stephen Amadei
> Systems Admin
> Dandy.NET
> Atlantic City, NJ
> 
> 
--
Mark Andrews, Internet Engines Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at iengines.com


More information about the bind-users mailing list