if they are ad integrated then surely they are multi master and the sequence
number is irrelevant - unless you looked at the database between ad updates?
regards
Chris
MCSA
see attached excerpt from Microsoft White Paper "Windows 2000 DNS"
Active Directory Storage and Replication Integration
In addition to supporting a conventional way of maintaining and replicating
DNS zone files, the implementation of DNS in Windows 2000 has the option of
using the Active Directory services as the data storage and replication
engine. This approach provides the following benefits:
· DNS replication will be performed by Active Directory service, so there is
no need to support a separate replication topology for DNS servers.
· Active Directory service replication provides per-property replication
granularity.
· Active Directory service replication is secure.
· A primary DNS server is eliminated as a single point of failure. Original
DNS replication is single-master; it relies on a primary DNS server to
update all the secondary servers. Unlike original DNS replication, Active
Directory service replication is multi-master; an update can be made to any
domain controller in it, and the change will be propagated to other domain
controllers. In this way if DNS is integrated into Active Directory service
the replication engine will always synchronize the DNS zone information.
Thus Active Directory service integration significantly simplifies the
administration of a DNS namespace. At the same time standard zone transfer
to other servers (non Windows 2000 DNS servers and previous versions of the
Microsoft DNS servers) is still supported.
BobK said:
Hopefully I am in the correct newgroup. I am wondering about SOA serial
numbers with regards to IXFRs. If an organization had implemented AD
Integrated zones thereby making them all writable and two different DNS
servers both had the their serial number incremented to the same number, say
26 yet the updates themselves were different, how would the separate changes
ever get replicated to other DNS servers.
