Seperate replication schedual

  • Thread starter Thread starter aptrsn
  • Start date Start date
A

aptrsn

Is it possible to integrate DNS in AD on a seperate replication schedual?
The reason I ask is that for limited bandwidth issues, I would like
replication traffic to remote sites be kept at a minimum ( 2x per day),
however DNS replication would be once an hour? I was told the best way to
accomplish what I am looking to do is to uncheck AD integration, but I have
heard that you can create a DNS partition in AD. Anyone have experience
doing this?
 
In
aptrsn said:
Is it possible to integrate DNS in AD on a seperate replication
schedual? The reason I ask is that for limited bandwidth issues, I
would like replication traffic to remote sites be kept at a minimum (
2x per day), however DNS replication would be once an hour? I was
told the best way to accomplish what I am looking to do is to uncheck
AD integration, but I have heard that you can create a DNS partition
in AD. Anyone have experience doing this?
Click to expand...

You can create a partition (W2k3 only), but since the partition is just a
logical partition, it still follows the AD replication rules based on what
Site the machine is in adn as far as I know there's no way to circumvent
that part of it, since replication frequency and schedules are set on the
Site link.

I would like to see what you were told about doing it with a partition.
Curious who told you and what steps they provided.

--
Regards,
Ace

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

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
I heard about it in a introductory class on Windows 2003 Server at "Learning
Tree." The reason why this was suggested was that you could then segregate
the replication traffic and allow the DNS partition to replicate on a more
frequent basis than the other partitions of your AD. As to the how, because
the class was limited in scope (only the rudimentary aspects of server 2003,
they want you to take other classes for AD, Networking, etc) the instuctor
did not have the time to go into it in detail.We are going to a full W2k3
enviroment, so I guess it would feasable in our circumstances, but I have
not found the information at Microsoft or in the books that I have been
reading.

This would'nt even be an issue if wern't for the fact that the DNS zones
between my DC's and root DC are not transfering there records from their
foreward lookup zones (FLZ) like I expected them too. All of them currently
are running DNS without AD integration. I originally set up the FLZ on the
remote DC by creating a secondary zone from the root DC and then changed it
to a primary zone so that it could be updated directly with clients at that
remote location using DDNS. This seems to be working fine except that the
new A records for clients being added to to the remote DC's FLZ are not
being updated to the root DC's DNS. Zone transfers (to all DNS listed in the
FQDN tab) are enabled with notify checked, yet they are not being updated to
the root DC's DNS.

Your insights would be appreciated.

Thanks





"Ace Fekay [MVP]"
 
In
aptrsn said:
I heard about it in a introductory class on Windows 2003 Server at
"Learning Tree." The reason why this was suggested was that you could
then segregate the replication traffic and allow the DNS partition to
replicate on a more frequent basis than the other partitions of your
AD. As to the how, because the class was limited in scope (only the
rudimentary aspects of server 2003, they want you to take other
classes for AD, Networking, etc) the instuctor did not have the time
to go into it in detail.We are going to a full W2k3 enviroment, so I
guess it would feasable in our circumstances, but I have not found
the information at Microsoft or in the books that I have been reading.

This would'nt even be an issue if wern't for the fact that the DNS
zones between my DC's and root DC are not transfering there records
from their foreward lookup zones (FLZ) like I expected them too. All
of them currently are running DNS without AD integration. I
originally set up the FLZ on the remote DC by creating a secondary
zone from the root DC and then changed it to a primary zone so that
it could be updated directly with clients at that remote location
using DDNS. This seems to be working fine except that the new A
records for clients being added to to the remote DC's FLZ are not
being updated to the root DC's DNS. Zone transfers (to all DNS listed
in the FQDN tab) are enabled with notify checked, yet they are not
being updated to the root DC's DNS.

Your insights would be appreciated.

Thanks
Click to expand...


I would have to look into it. I have the courseware... just can't remember!

Here you go... this may help out: Sorry for the original misinformation...

Create the default DNS application directory partitions:
http://www.microsoft.com/technet/tr...ocs/datacenter/sag_dns_pro_adddefaultndnc.asp


--
Regards,
Ace

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

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