Nick,
You don't assign subnets to zones. But you can assign an IP range to
multiple zones. Click on the Admin link and then choose List next to IP
Ranges. Find your range and choose Edit. At the bottom of the page,
you can add the range to as many zones as you want. You have to choose
a default domain, which is something we need to fix, now that I'm
looking at it. The domain you choose needs to already be assigned to
the zone. The default domain only has meaning for dynamic ranges -
since we don't do DDNS, Maintain automatically generates reverse lookups
like 1-2-3-4.dynamic.domain.foo, where "dynamic.domain.foo" is the
"default domain" you specify. Currently, the default domain is
associated with both zone and range, but it should just be tied to the
range. Gah.
Anyway, the steps overall are like this:
* Create subnet
* Create range
* Create domain
* Create zone
* Add domain to zone
* Edit range page to add range to zone(s)
Sigh, we really need a setup wizard. That's on the wishlist, too.
P.S. There's a checkbox on the range page that says "Require all domains
in zone" - I forget what that is supposed to do. Looks like another
legacy thing we need to remove.
Oh, and ouch - there is another bug on the range page - it's not showing
the current settings for a range when you're on the edit action. I'll
file a bug.
________________
Kirsten Petersen
Network Services * Oregon State University
http://oregonstate.edu/net <http://oregonstate.edu/net> *
irc.oregonstate.edu #osu-is
"But it's the truth even if it didn't happen." -Ken Kesey
________________________________
From: Nick Nikjoo [mailto:nickn at nortel.com]
Sent: Wednesday, March 05, 2008 10:44 AM
To: Petersen, Kirsten J - NET
Subject: RE: [Maintain] IPv6 Support
Hi Kirsten ,
Your reply and answer is greatly appreciated.
As per my second question; I guess, can not we have same subnets in
different zones
We have multiple labs across various locations, and we all use the same
RFC1918 IP ranges.
We would like to have single server to keep track of all the 10.x.x.x,
172.16.x.x & 192.168.x.x. This means we have multiple instances of
10.x.x.x in other labs.
Thanks,
Nick
________________________________
From: Petersen, Kirsten J - NET
[mailto:Kirsten.Petersen at oregonstate.edu]
Sent: Wednesday, March 05, 2008 1:17 PM
To: Nikjoo, Nick (CAR:NL13); maintain at osuosl.org
Subject: RE: [Maintain] IPv6 Support
Nick,
We plan to add support for IPv6, but we'd like to change the database
schema when we do. So.. it's going to be in Maintain version 4.
Probably at least a year away.
That said, we are adding support to build bind files now, so you could
include IPv6 entries from a static file. We'll be trying that out here
at OSU, so I'll let you know how it goes. :)
________________
Kirsten Petersen
Network Services * Oregon State University
http://oregonstate.edu/net * irc.oregonstate.edu #osu-is
"But it's the truth even if it didn't happen." -Ken Kesey
________________________________
From: maintain-bounces at osuosl.org [mailto:maintain-bounces at osuosl.org]
On Behalf Of Nick Nikjoo
Sent: Saturday, March 01, 2008 3:11 AM
To: maintain at osuosl.org
Subject: [Maintain] IPv6 Support
Hi,
Planning to use the tool and I have two questions. Thanking you in
advance for the replies.
Is there a support for IPv6?
Can each zone support same subnets?
Example: Have two labs and using the same 10.0.0.0/8 range. Is this
supported in the tool?
Regards,
Nick S.A. Nikjoo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osuosl.org/pipermail/maintain/attachments/20080306/fd7042f5/attachment.htm