<div>
Are these records in AD-integrated zones? &nbsp;Are you aware that if you don't have scavenging set on a zone that the timestamps won't replicate?
</div>


<div>
They are in an AD integrated zone and scavenging is not turned on. &nbsp;We are cleaning up DNS before we scavenge.<br />
<br />
Are you telling me that absent scavenging, these time stamps won't replicate to other DCs?
</div>


<div>
that's my problem. &nbsp;If I turn it on, I lose records with old time stamps that are active and I cannot lose. &nbsp;<br />
<br />
I inherited this DNS and it's YEARS old and NEVER scavenged. &nbsp;I need all of my devices to update and replicate but I can't scavenge yet cos I lose active records with old time stamps.
</div>


<div>
You're not understanding. &nbsp;You can turn on scavenging for a zone, but unless you set the server to actually perform the scavenging process, no records will be deleted. &nbsp;Read through the link I provided. &nbsp;It pretty much explains everything.
</div>


<div>
ok, read the article, and at the risk of sounding stupid, how can I get JUST timestamp replication working for now?
</div>


<div>
Turn on scavenging for the zone. &nbsp;Make sure no servers are set to perform scavenging - in other words, make sure the box for &quot;Enable automatic scavenging of stale records&quot; is not checked on any server.
</div>


<div>
you sir are a computer god! &nbsp;:)
</div>


<div>
<div class="content wysiwyg-content">
Environ is Four 2012 R2 domain controllers in a 2008 R2 DFL and FFL. &nbsp;I'm noticing some odd DNS issues. &nbsp;<br />
<br />
On my Houston DC, server1 and server2 (both Houston servers) have updated time stamps.<br />
<br />
On my Phoenix DC, those same two servers have a different time stamps, several months older.<br />
<br />
On a Phoenix DC, server3 and server4 (both Phoenix servers) have correct time stamps, but on the Houston DC, they are several months older. &nbsp;<br />
<br />
I see this pattern is consistently. &nbsp;It's like my DCs aren't in sync on time stamps. &nbsp;<br />
<br />
The thing is, replication is 100% all the way around and when I add a PC or server to DNS, it gets populated across the pond just fine. <br />
<br />
Anyone seen this or have any ideas?<br />
<br />
Thanks<br />
<br />
Cliff
</div>
</div>


Environ is Four 2012 R2 domain controllers in a 2008 R2 DFL and FFL.  I'm noticing some odd DNS issues.  

On my Houston DC, server1 and server2 (both Houston servers) have updated time stamps.

On my Phoenix DC, those same two servers have a different time stamps, several months older.

On a Phoenix DC, server3 and server4 (both Phoenix servers) have correct time stamps, but on the Houston DC, they are several months older.  

I see this pattern is consistently.  It's like my DCs aren't in sync on time stamps.  

The thing is, replication is 100% all the way around and when I add a PC or server to DNS, it gets populated across the pond just fine. 

Anyone seen this or have any ideas?

Thanks

Cliff

Odd DNS issues...

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.