DNS Record Timestamp Replication

hi there,

i'm getting ready enable scavenging on our internal ad-replicated dns zone. looking around @ our dns record timestamps, noticed dc listed primary of other member servers has current timestamp. when create test record on primary dns server, replicates you'd expect no issues. records on non-primary dcs have correct data, old timestamps.

is normal behaviour?

 - liam

hi ace,

thanks response. think have pretty handle on scavenging process , of records behave expected. however, when record updates on server 1, timestamp isn't updated on server 2. if design, i'm not sure how cross-site name resolution work without having dns servers point root.

 - liam

might have missed part reading info in blog pointing link:

"once timestamp set on record replicate around servers host zone. there 1 caveat this. if scavenging not enabled on zone hosts record never scavenge timestamp irrelevant. timestamp may updated on server client dynamically registers not replicate around other servers in zone."

don't afraid of dns scavenging. patient:
http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

 

---

ace fekay
mvp, mct, mcitp ea, mcts windows 2008 & exchange 2007 & exchange 2010, exchange 2010 enterprise administrator, mcse & mcsa 2003/2000, mcsa messaging 2003
microsoft certified trainer
microsoft mvp - directory services
complete list of technical blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

this posting provided as-is no warranties or guarantees , confers no rights.

Windows Server  >  Network Infrastructure Servers