DNS Setup Help

  • Thread starter Thread starter BigE
  • Start date Start date
B

BigE

We are switching our network from using registered IP
addresses to private 10.*.*.* addresses.

We currently use Active-Directory Integrated Zones with
one forward lookup zone (mydomain.com) and PTR zones for
each IP range (12.1.1.1/24, 12.1.1.2/24, etc.).

We want to switch to the same forward lookup zone
(mydomain.com) but for the PTR zones should we use 10-in-
addr-arpa or is it preferable to create an individual
zone for each subset (10.1.*.*, 10.2.*.*, etc)?

When using AD-integrated zones is it typical to have to
add the zone information onto each new server to accept
replication? For example if I add a DC with the DNS
server component the forward and reverse lookup zones do
not populate via replication; but if I enter the zone the
data all appears to reside within AD locally.

TIA,
E
 
In
BigE said:
We are switching our network from using registered IP
addresses to private 10.*.*.* addresses.

We currently use Active-Directory Integrated Zones with
one forward lookup zone (mydomain.com) and PTR zones for
each IP range (12.1.1.1/24, 12.1.1.2/24, etc.).

We want to switch to the same forward lookup zone
(mydomain.com) but for the PTR zones should we use 10-in-
addr-arpa or is it preferable to create an individual
zone for each subset (10.1.*.*, 10.2.*.*, etc)?
Click to expand...

You can do it either way. If you want all the records in the one zone, you
can choose 10. as the zone. If not, say to easier see each zone, you can
break them down.
When using AD-integrated zones is it typical to have to
add the zone information onto each new server to accept
replication?
Yes

For example if I add a DC with the DNS
server component the forward and reverse lookup zones do
not populate via replication;
Click to expand...

If I understand what you're saying, then they should if they are AD
Integrated zones.
but if I enter the zone the
data all appears to reside within AD locally.
Click to expand...

Well, that's the idea of AD Integrated zones. They do not exist as a text
file in system32\dns as are Primary Zones. They are in the actual AD
database. The term "AD Locally" is subjective, since the AD database is
replicated to all DCs, so therefore, you can say "AD Locally" but remember,
it's a multi master copy. Each DC can make changes in it's own database,
which are then replicated thru the AD replication process to other DCs. Keep
in mind, that the AD Database is broken down into 3 sections (W2k):
1. Domain NC
2. Config Containter
3. Schema Container

DNS zone info is stored in the Domain NC. THat partition is ONLY replicated
between DCs in that specific domain. If you have child domains or other
domians, this partition DOES NOT rpelicate to them, so therefore, the zone
info will NOT be present in their Domain NC. The other 2 are replicated
Forest wide.

In W2k3, there are two addtional partitions which we can state an AD
Integrated zone can be replicated to other domains in the Forest.

Don't forget to change the IPs in the nameservers tab as well.....

TIA,
E
Click to expand...

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
I am using AD-integrated zones. When I create a new DC I
add the DNS server component during setup. No zones are
created in the forward or reverse lookup zones--I must
manually add these and then the records populate. Is
that normal behavior?

If I started by breaking out 10.1.*.*, 10.2.*.*, etc and
later want to consolidate into one zone is it easily
accomplished? Can I simply delete the existing zones and
create the one new 10.*.*.* zone and run
ipconfig /registerdns on all domain controllers and
servers?
 
In
I am using AD-integrated zones. When I create a new DC I
add the DNS server component during setup. No zones are
created in the forward or reverse lookup zones--I must
manually add these and then the records populate. Is
that normal behavior?

If I started by breaking out 10.1.*.*, 10.2.*.*, etc and
later want to consolidate into one zone is it easily
accomplished? Can I simply delete the existing zones and
create the one new 10.*.*.* zone and run
ipconfig /registerdns on all domain controllers and
servers?
Click to expand...

Yes it is normal behavior with the need to manually create the zone name.
Once you create it on a new DC and specifiy it's an AD Integrated zone, then
the zone will populate from what it finds in AD.

If you break it out, then want to change it to a 10., you can re-register
them by doing exactly that on each and every machine that you want
registered.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top