Re: Overlapping Reverse Zone Files
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sat, 10 Feb 2007 17:02:02 -0600
"Will" <westes-usc@xxxxxxxxxxxxxx> wrote in message
news:u-qdnepA5p8b1VPYnZ2dnUVZ_oCmnZ2d@xxxxxxxxxxxxxxx
We have multiple subnets in the 192.168.0.0 class C that belong to Forest
f1.domain.com. We have a single subnet in the same space that belongs to
Forest f2.domain.com. My question is how do I handle the reverse
zonefiles for this in the domain for forest f1.domain.com?
First of all lets eliminate some common sources of misconceptions,
maybe people tend act as if the following are not true -- they are:
1) Reverse zone files aren't very important for internal machines*
2) Zones don't belong to "DNS" servers except in that you CHOOSE
to have that Server hold a copy of the zone (e.g., Primary,
Secondary etc.)
3) There is NO technical relationship in DNS between a forward and a
reverse zone. (The only relationship between forward and
reverse
zones is the in the minds of us human beings.)
What would be
easiest for me would be to define for f1 a single active-directory
integrated class z reverse zone 192.168.0.0.
That should work, but I have had some trouble with dynamic registration
unless you use the actual Class-C looking subnet zones -- this should NOT
be required but it seems to be.
You might also chose to replicate such zones "Forest Wide" IF you have
all Win2003 DC-DNS servers AND the zones are not obnoxiously large.
Then, in addition to that,
define a secondary zone that draws the one overlapping subnet from f2.
That is another choice, but forest wide integration gets you multi-mastered
registration, replication, etc.
How is Windows going to deal with that overlap?
There is, or can be, no overlap. If you create two separate zones covering
the same ranges they will not replicate at all.
Is it going to merge the
two reverse zones together, just ignoring the theoretical possibility of a
collision between them? If there is a collision, which reverse zone would
win?
Clients will resolve from the one held by there DNS server or that is "found
first".
So don't do that. Use one Primary-Secondary set for each zone, or use
one (perhaps forest wide) AD-Integrated (with optional secondaries) if you
prefer.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- Overlapping Reverse Zone Files
- From: Will
- Overlapping Reverse Zone Files
- Prev by Date: Re: DNS server setup questions
- Next by Date: Re: Overlapping Reverse Zone Files
- Previous by thread: Overlapping Reverse Zone Files
- Next by thread: Re: Overlapping Reverse Zone Files
- Index(es):
Relevant Pages
|
