Re: DNS SOA serial numbers out of sync

In news:49834d70$0$18007$607ed4bc@xxxxxx,
news.optonline.net <Nick>, posted the following:
I have 3 DNS servers in 3 different domains, all AD integrated.

Problem:
The main DNS server (DNS1.company.com) is transferring/replicating
records with DNS2.company.com but is not transfering the records to
DNS3.company.com. It used to but for some reason stopped.

I noticed the SOA serial number on DNS3 is higher than that of DNS1
and DNS2. DNS1 & DNS2 have the same SOA serial numbers and are
working perfectly.

My questions:
would the higher serial # on DNS3 cause it not to pull records from
DNS1 because DNS3 thinks it's more up to date ?
Can I up the SOA serial number on DNS1 to a value higher than the
value on DNS3 and have all my DNS servers sync nicely, and not damage
anything ?
Thanks
Nick

If the zone is AD Integrated, there is no "zone transfer' occuring to send the data between DNS servers. This is because an AD integrated zone stores the actual zone data in the actual physical AD database and will replicate to all DC/DNS servers in the forest.

Also, please keep in mind that SOA serial numbers will fluctuate between DC/DNS servers in an AD integrated zone. This is default behavior. This is normal due to each DC/DNS is a master replica. Each one can make a change to the zone. Whenever a change is made, the SOA will be bumped on, only on THAT DC/DNS. Of course the new data will replicate and will bump up on the other DC/DNS, but I highly doubt if you will ever see the same exact SOA number on any two DC/DNS servers at the same time. If they are, then that would tell me the zones are PrimarySecondary and not AD integrated.

Read the following article please:
Active Directory-integrated DNS zone serial number behavior
http://support.microsoft.com/kb/282826

If you are having replication problems, or if there are duplicate entries in AD for the zone (possibly due to creating the zone manually, or setting the zone on one DC to one replication scope, and the zone on another DC to a different replication scope), this will definitely cause problems.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCT
Microsoft Certified Trainer
aceman@xxxxxxxxxxxxxxxxxxxxxxx

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

.

Relevant Pages

  • Re: Event 4515 - Duplicate zones, both appear valid
    ... My company runs an Active Directory Forest with 3 child domains. ... scopes set to "To all DNS servers in the Active Directory Forest ... The problematic child domain it concerns here has it's DNS Zone ... Replication Scope set to "To all domain controllers in the Active ...
    (microsoft.public.windows.server.dns)
  • Re: Repost: Missing ForestDNSZones and DomainDNSZones partitions under child AD 2003 domain
    ... The reverse zone for the hbrpaw.hbr-inc.com subnet was already there. ... PAW2 or PAWDC DNS servers, I receive the message "would you like to ... It took me two days to figure out what happened when I finally asked what occured prior to the replication issue, which was when the customer told me they had upgraded one firewall. ... article discusses the new features and functionality that are available in PortQry Command Line Port Scanner version 2.0. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS problem.
    ... zone in DC4)? ... and should have replication errors on the eventviewer... ... We have many DNS servers around company. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS problem.
    ... DNS zone in DC4)? ... and should have replication errors on the eventviewer... ... all the dns servers are in the same domain and same zone. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS server RPC problem
    ... There is just one DNS/DC. ... permanently offline.Hence there is no AD replication. ... > How many DC/DNS servers are there in your environment? ... > If you change the zone to a Primary zone, ...
    (microsoft.public.windows.server.dns)
Loading